On Wed, Nov 07, 2001 at 11:12:24AM +1100, Nathan Scott wrote:
> A manual page describing the system call interface can be found here[4].
> We're very interested in feedback on this. In partiular, Linus - would
The cursor support looks quite complicated. It doesn't even forbid
storing the contents of the cursor buffer somewhere and has all
the standard problems with stateless cursors requiring nasty hacks
with dynamic data structures with parallel modification.
Stateless cursors are just nasty!
I think it would be better to have a statefull readdir instead.
The kernel supports it via the ->private_data field of struct file
(not through fork,but that looks like a generic vfs bug)
EA_FIRST_ENTRY to reset the fd the first entry, EA_READ_ENTRY to
read the next one.
It would not be inherently thread safe, but also not be worse
in this regard than standard readdir (requiring user locks)
It would also be possible to do a threadsafe interface although it would be
a bit uglier: EA_GET_LISTSIZE to get the
size of the buffer required, EA_GET_FULL_LIST to fetch a full
buffer with the names of all EAs, EAGAIN on race.
I think doing it in one of these ways would be far easier for the
user and easier for future kernel implementations.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Nov 07 2001 - 21:00:33 EST