From: Eric Dumazet <dada1@cosmosbay.com>
To: David Lang <dlang@digitalinsight.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shrinks sizeof(files_struct) and better layout
Date: Fri, 06 Jan 2006 08:37:42 +0100 [thread overview]
Message-ID: <43BE1E46.3060904@cosmosbay.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0601052318570.1708@qynat.qvtvafvgr.pbz>
David Lang a écrit :
> Ok, so if you have large numbers of CPU's and large page sizes it's not
> useful. however, what about a 2-4 cpu machine with 4k page sizes, 8-32G
> of ram (a not unreasonable Opteron system config) that will be running
> 5,000-20,000 processes/threads?
Dont forget 'struct files_struct' are shared between threads of one process.
So may benefit from this 'special cache' only if you plan to run 20.000 processes.
>
> I know people argue that programs that do such things are bad (and I
> definantly agree that they aren't optimized), but the reality is that
> some workloads are like that. if a machine is being built for such uses
> configuring the kernel to better tolorate such use may be useful
If 20.000 process runs on a machine, I doubt the main problem of sysadmin is
about the 'struct files_struct' placement in memory :)
Eric
next prev parent reply other threads:[~2006-01-06 7:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051108185349.6e86cec3.akpm@osdl.org>
[not found] ` <437226B1.4040901@cosmosbay.com>
[not found] ` <20051109220742.067c5f3a.akpm@osdl.org>
[not found] ` <4373698F.9010608@cosmosbay.com>
2006-01-04 0:06 ` [PATCH] Shrinks sizeof(files_struct) and better layout Eric Dumazet
2006-01-04 9:11 ` Jan Engelhardt
2006-01-04 10:12 ` Eric Dumazet
2006-01-04 10:28 ` Folkert van Heusden
2006-01-04 10:45 ` Andi Kleen
2006-01-04 11:13 ` Eric Dumazet
2006-01-04 11:15 ` Andi Kleen
2006-01-04 11:19 ` Eric Dumazet
2006-01-04 11:22 ` Andi Kleen
2006-01-04 11:41 ` Eric Dumazet
2006-01-04 11:58 ` Andi Kleen
2006-01-06 3:01 ` David Lang
2006-01-06 6:35 ` Eric Dumazet
2006-01-06 7:26 ` David Lang
2006-01-06 7:37 ` Eric Dumazet [this message]
2006-01-06 8:28 ` David Lang
2006-01-04 11:45 ` Andrew Morton
2006-01-04 13:14 ` Eric Dumazet
2006-01-04 23:24 ` [2.6 patch] Define BITS_PER_BYTE Adrian Bunk
2006-01-05 7:03 ` Jan Engelhardt
2006-01-05 15:18 ` Bryan O'Sullivan
2006-01-05 19:19 ` H. Peter Anvin
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=43BE1E46.3060904@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=ak@suse.de \
--cc=dlang@digitalinsight.com \
--cc=linux-kernel@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