From mboxrd@z Thu Jan 1 00:00:00 1970 From: jenn sirp Subject: repost for readdir Date: 23 Jun 2004 16:09:46 -0700 Message-ID: <1088032186.12051.8.camel@murdock.llnl.gov> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com List-Id: Content-Type: text/plain; charset="us-ascii" To: reiserfs-list@namesys.com 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