From: George Beshers <gbeshers@sgi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd on very large systems: again
Date: Wed, 02 May 2007 21:39:48 +0000 [thread overview]
Message-ID: <46390524.8060305@sgi.com> (raw)
In-Reply-To: <4637D051.7060103@sgi.com>
Kay Sievers wrote:
> On 5/2/07, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> On 5/2/07, George Beshers <gbeshers@sgi.com> wrote:
>> >
>> > After some testing the following patch seems safe for dealing with
>> computers
>> > with more than 500 processors. It occurred to me that it might be
>> > easier and
>> > just as useful to note when udev is running on a large computer
>> (e.g., >= 8p
>> > and >= 16Gb of memory) and simply not worry about throttling at
>> that point.
>> >
>> > The patch should apply cleanly against udev-110.
>> >
>> > Comments welcome.
>>
>> Looks fine so far, but I still don't see how reading a seq-proc-file
>> could miss entries. Are you expecting this to happen? Did you ever see
>> this for any of these files?
>
> If I read linux/fs/proc/proc_misc.c correctly, /proc/stat fills a
> buffer of 128kB in one call and passes the data to the file.
>
> I wonder how long it will take, that you guys hit the 128k limit. :)
>
> Thanks,
> Kay
Hmmm... well on the 128p system where I did my testing the size of
/proc/stat ranged from 5317 to 5451 (that was with 151 active procs).
At that scale 2048 should be OK.
BTW. I should have said that the log was generated with a kernel
build (make -j 128 or something like that) going.
George
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-05-02 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 23:42 udevd on very large systems: again George Beshers
2007-05-02 19:37 ` Kay Sievers
2007-05-02 21:11 ` Kay Sievers
2007-05-02 21:26 ` George Beshers
2007-05-02 21:39 ` George Beshers [this message]
2007-05-02 23:42 ` Kay Sievers
2007-05-02 23:51 ` Kay Sievers
2007-05-03 19:49 ` George Beshers
2007-05-03 21:12 ` Kay Sievers
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=46390524.8060305@sgi.com \
--to=gbeshers@sgi.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).