If not readdir() then what?
- From: "Ulrich Drepper" <drepper@xxxxxxxxx>
- Date: Sat, 7 Apr 2007 09:57:32 -0700
In their closed chambers (well, workshops,
http://lwn.net/Articles/226351/), the filesystem developers complain
about readdir. I fully appreciate the difficulties. But what I fail
to see so far is any proposal for an alternative interface.
The phase to get new functionality included in the next revision of
POSIX is over. But that does not mean we should not try to get some
sensible new implementation in place. There is, for example, the
"High End Computing Extensions Working Group" (the guys who showed up
here with their statlite and readdirplus proposals). This is an
official working group at the OpenGroup which can produce a document
which can be the basis of inclusion in the next revision and become a
OpenGroup specification earlier than that.
So, if anybody has a proposal for better interfaces let's hear them.
"Now" is a very good time to start working on this.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: If not readdir() then what?
- From: Theodore Tso
- Re: If not readdir() then what?
- Prev by Date: Re: Two questions regarding Opening files within Kernel!
- Next by Date: Re: Reiser4. BEST FILESYSTEM EVER.
- Previous by thread: [PATCH] block layer: Add bdev capacity helper function get_sect_count
- Next by thread: Re: If not readdir() then what?
- Index(es):
Relevant Pages
|
