From: Andi Kleen <andi@firstfloor.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>,
Jeremy Eder <jeder@redhat.com>
Subject: Re: [PATCH 5/5][RFC][CFT] resizable namespace.c hashes
Date: Fri, 07 Mar 2014 09:17:19 -0800 [thread overview]
Message-ID: <87bnxi6i8w.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140305035219.GE26528@ZenIV.linux.org.uk> (Al Viro's message of "Wed, 5 Mar 2014 03:52:19 +0000")
Al Viro <viro@ZenIV.linux.org.uk> writes:
> * switch allocation to alloc_large_system_hash()
> * make sizes overridable by boot parameters (mhash_entries=, mphash_entries=)
> * switch mountpoint_hashtable from list_head to hlist_head
So how much memory does this use on a standard system (<4GB memory)?
How much memory does it use on a large system (0.5TB)?
How good is your hash function. Would jhash be more appropiate
and allow smaller hash tables?
Perhaps just want a tree here.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-03-07 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 3:47 [PATCHES][RFC][CFT] scalability fixes for shitloads of mounts Al Viro
2014-03-05 3:49 ` [PATCH 1/5][RFC][CFT] percpu fixes, part 1 Al Viro
2014-03-06 19:20 ` Tejun Heo
2014-03-06 20:30 ` Al Viro
2014-03-06 20:47 ` Tejun Heo
2014-03-07 2:52 ` Al Viro
2014-03-07 12:30 ` Tejun Heo
2014-03-14 18:45 ` Al Viro
2014-03-14 18:47 ` Tejun Heo
2014-03-14 18:53 ` Al Viro
2014-03-17 20:12 ` [PATCH percpu/for-3.15] percpu: allocation size should be even Tejun Heo
2014-03-05 3:50 ` [PATCH 2/5][RFC][CFT] fold pcpu_split_block() into the only caller Al Viro
2014-03-06 19:21 ` Tejun Heo
2014-03-05 3:51 ` [PATCH 3/5][RFC][CFT] smarter propagate_mnt() Al Viro
2014-03-05 3:51 ` [PATCH 4/5][RFC][CFT] reduce m_start() cost Al Viro
2014-03-05 3:52 ` [PATCH 5/5][RFC][CFT] resizable namespace.c hashes Al Viro
2014-03-07 17:17 ` Andi Kleen [this message]
2014-03-07 18:38 ` Al Viro
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=87bnxi6i8w.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=jeder@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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