From: "John Garrison" <jgarrison-mRW4Vj+HBIk@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: [SPAM] NILFS2 Cleaner Explanation Request
Date: Fri, 16 Jan 2009 07:16:06 -0600 [thread overview]
Message-ID: <000401c977dc$97465850$c5d308f0$@edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]
Could you provide an explanation of the cleanerd's algorithm and method in
cleaning the file system. What all does it do during a pass, what kind of
complexity is the operation, does it generally follow the cleaner suggested
in the original SPRITE LFS paper (where the write cost on a cleaning
operation is 2/(1-u) where u is the utilization of segments), etc. The
reason I ask is that in my research, we have done some work on page cache
algorithms to improve the cleaning in a log structured file system. NILFS2
seems to work quite well in our preliminary tests with Flash SSDs (as one
would expect), but before we move forward to actual implementation of our
page cache ideas, it would be good to understand how the NILFS2 cleaner
works and how we might interact with it. I have done some digging in the
code, but I think a relatively high level explanation of the strategy and
motivation behind the design choices would be very helpful in understanding
exactly what is going on and how our algorithms might interact with it.
Thanks in advance.
John Garrison
[-- Attachment #1.2: Type: text/html, Size: 2797 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users
reply other threads:[~2009-01-16 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000401c977dc$97465850$c5d308f0$@edu' \
--to=jgarrison-mrw4vj+hbik@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/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