From: Marc Lehmann <schmorp@schmorp.de>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: dir_level explained?
Date: Sun, 4 Oct 2015 11:56:47 +0200 [thread overview]
Message-ID: <20151004095647.GC3177@schmorp.de> (raw)
Hi!
In all my tests I intentionally didn't play with dir_level, to get an idea of
baseline performance. I also wasn't worried because my standard response to
slow random reads is dmcache, but now that I realised I can't use dmcache
with these drives, I got more interested in dir_level.
If I understand it correctly, higher values of dir_level potentially waste
more space but gain performance. However, I have no clue about what the
trade-off really is.
Could you explain what kind of extra space usage I can expect from higher
levels of dir_level, or what the values mean?
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
------------------------------------------------------------------------------
next reply other threads:[~2015-10-04 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 9:56 Marc Lehmann [this message]
2015-10-05 23:05 ` dir_level explained? Jaegeuk Kim
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=20151004095647.GC3177@schmorp.de \
--to=schmorp@schmorp.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.