Re: If not readdir() then what?
- From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
- Date: Sun, 8 Apr 2007 16:36:47 -0400
On Sat, Apr 07, 2007 at 04:36:33PM -0400, Theodore Tso wrote:
1) Deprecate telldir/seekdir() altogether. Relatively few progams use
this functionality, and it is highly questionable how useful it is,
anyway. If you use telldir/seekdir and keep the cookie for a long
time, even the POSIX-provided guarantees about files that are created
and deleted between the telldir() and seekdir() points in time makes
its utility highly dubious.
How will nfsd implement readdir?
2) If application programs must have telldir/seekdir, than expand the
size of the cookie from 32-bits to a minimum of 128 bits, and
preferably larger --- say 512 bits, to accomodate systems that might
be using 512-bit variant of SHA-2.
NFS readdir cookies are currently 64 bits.
It'd be interesting to think about how to modify the protocol to make
this all easier, but any network filesystem protocol will need to give
clients some way to read through big directories one piece at a time.
Might also be nice if it worked even if the server rebooted partway
through....
--b.
-
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/
- References:
- If not readdir() then what?
- From: Ulrich Drepper
- Re: If not readdir() then what?
- From: Theodore Tso
- If not readdir() then what?
- Prev by Date: Re: kernel BUG at net/core/skbuff.c in linux-2.6.21-rc6
- Next by Date: Re: [PATCH 0/4] Fix MTRR suspend support for specific machines (some AMD64, maybe others also)
- Previous by thread: Re: If not readdir() then what?
- Next by thread: [PATCH 1/2] Clean up asm-x86_64/bugs.h
- Index(es):
Relevant Pages
|
