From: dizzy <dizzy@roedu.net>
To: xfs@oss.sgi.com
Subject: readdir() ordering guarantees on XFS
Date: Fri, 6 Jun 2008 16:34:13 +0300 [thread overview]
Message-ID: <200806061634.13990.dizzy@roedu.net> (raw)
Hello
POSIX leaves unspecified the order of getting the entries with readdir(). This
is normal since different filesystems may implement their own techniques to
organize entries in a directory (linear, hash, various search trees, etc).
But if I can makes sure that several Linux machines will have the same FS (ie
XFS), mount options and same kernels can assume that traversing the same file
hierarchy structure (that is a file structure with the exact same directories
and files as names, structure, attributes, except maybe "ctime" which we
can't really control in Linux) can I expect that traversing using readdir()
will give me the entries in the exact same order? Or are there any other
conditions that I have to check for that would guarantee it? (such as, for a
linear directory aproach one has to have created the directory entries in the
same order on all the machines to expect same order on readdir()).
Currently, we workaround this issue by reading all the directory entries,
sorting them and traversing the entries in the sorted order. This however has
been proven to slow the traversal (depth first traversal) operation about 30%
than doing it in the order received from readdir() (I even had the test code
read the whole directory contents, sort them in memory but still have it
traverse in the order readdir() reported and it is 30% faster than traversing
in the sorted order).
Any idea?
Thanks!
PS: please Cc: me as I'm not subscribed to the list, thank you
--
Mihai RUSU Email: dizzy@roedu.net
"Linux is obsolete" -- AST
next reply other threads:[~2008-06-06 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 13:34 dizzy [this message]
2008-06-10 3:55 ` readdir() ordering guarantees on XFS Dave Chinner
2008-06-10 8:20 ` dizzy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806061634.13990.dizzy@roedu.net \
--to=dizzy@roedu.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox