From: Andi Kleen <andi@firstfloor.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Nathan Fontenot <nfont@austin.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] memory hotplug disable boot option
Date: Mon, 28 Jun 2010 16:16:15 +0200 [thread overview]
Message-ID: <20100628141615.GA7608@basil.fritz.box> (raw)
In-Reply-To: <m14ognkd26.fsf@fess.ebiederm.org>
> I have a prototype patch sitting around somewhere. I think ultimately
> it makes sense to do something like extN's htree directory structure
> in sysfs. I wanted to get the tagged sysfs support in before I worked
> on scalability because that slightly changes the requirements.
>
> Improving the scalability here is certainly worth doing, but I am slightly
> concerned there is something else algorithmically wrong if this is still
> going to take 33 minutes to boot with 2TB.
I'm don't think thousands of entries in sysfs is really a good idea. Even if you fix
the the insert algorithm issues a simple ls will still be very slow and there
will be likely other issues too. And nobody can claim that's a good interface.
This really needs a better a interface.
e.g. add some wildcard entry as it was earlier proposed.
and only generate the wildcard when some threshold is exceeded.
-Andi
next prev parent reply other threads:[~2010-06-28 14:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 1:06 [PATCH] memory hotplug disable boot option Nathan Fontenot
2010-06-25 2:04 ` KOSAKI Motohiro
2010-06-25 9:19 ` Andi Kleen
2010-06-25 14:51 ` Nathan Fontenot
2010-06-25 14:56 ` Andi Kleen
2010-06-25 15:21 ` Nathan Fontenot
2010-06-25 15:28 ` Andi Kleen
2010-06-25 16:00 ` Nathan Fontenot
2010-06-28 2:20 ` KOSAKI Motohiro
2010-06-28 4:15 ` Eric W. Biederman
2010-06-28 14:16 ` Andi Kleen [this message]
2010-06-28 19:43 ` Eric W. Biederman
2010-06-28 15:02 ` Greg KH
2010-06-28 15:37 ` Nathan Fontenot
2010-06-28 15:44 ` Greg KH
2010-06-29 0:04 ` Dave Hansen
2010-06-29 2:56 ` KOSAKI Motohiro
2010-06-29 15:38 ` Nathan Fontenot
2010-06-30 0:00 ` KOSAKI Motohiro
2010-06-29 16:03 ` Dave Hansen
2010-06-29 18:04 ` Greg KH
2010-06-30 0:32 ` KAMEZAWA Hiroyuki
2010-06-30 15:47 ` Greg KH
2010-07-01 0:31 ` KAMEZAWA Hiroyuki
2010-07-01 3:17 ` Nathan Fontenot
2010-07-01 3:30 ` KAMEZAWA Hiroyuki
2010-07-01 23:28 ` Greg KH
2010-07-01 5:15 ` KAMEZAWA Hiroyuki
2010-07-01 13:23 ` Dave Hansen
2010-07-06 15:20 ` Nathan Fontenot
2010-07-06 15:33 ` Dave Hansen
2010-07-06 15:47 ` Nathan Fontenot
2010-07-01 23:26 ` Greg KH
2010-07-02 5:50 ` KAMEZAWA Hiroyuki
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=20100628141615.GA7608@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfont@austin.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox