All of lore.kernel.org
 help / color / mirror / Atom feed
From: jenn sirp <sirp1@llnl.gov>
To: reiserfs-list@namesys.com
Subject: repost for readdir
Date: 23 Jun 2004 16:09:46 -0700	[thread overview]
Message-ID: <1088032186.12051.8.camel@murdock.llnl.gov> (raw)

Hi,

I'd like to thank you guys for your help earlier this year with the
initial phase of my project. I was able to implement FIFO queueing
functionality in Reiser v3. It is not very elegant, but I am still
learning. I was able to steer my supervisor in the direction of Reiser4.
It appears that the design principles of the new system will make it very
valuable for many at the Lab.

That said, and back to Hans' suggestion of a readdir implementation for
FIFO and LIFO file queuing... I have some questions. If anyone can answer
them, has advice, or suggestions that would be so great.

Here's where I am at, and what I don't know:

From what I can tell, files in the reiserfs 'Directory Item' aren't preserved in
the order they are written due to deletes and other operations. So if I
were to access the Directory Item to generate a list for readdir I couldn't be certain that they would be in first
created -to- last created order.

If readdir has to sort the files in the directory every time it is called
it seems like it would be a bit of a performance hit. Should another
structure be maintained that preserves the order as the files are
written... and should readdir use that as it's basis for returning the
directory contents?

If this is a question that doesn't belong here... please let me know and I apologize.

Thanks,

Jenn


             reply	other threads:[~2004-06-23 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 23:09 jenn sirp [this message]
2004-06-24 17:20 ` repost for readdir Vladimir V. Saveliev
2004-06-24 18:27   ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2004-06-24 19:28 jenn sirp
2004-06-24 19:30 jenn sirp

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=1088032186.12051.8.camel@murdock.llnl.gov \
    --to=sirp1@llnl.gov \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.