From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Tim Hockin <thockin@sun.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH 1/2] Remove NGROUPS hardlimit (resend w/o qsort)
Date: 15 Nov 2002 01:04:13 +0000 [thread overview]
Message-ID: <1037322253.17766.3.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20021114193156.A2801@devserv.devel.redhat.com>
On Fri, 2002-11-15 at 00:31, Pete Zaitcev wrote:
> > Date: Thu, 14 Nov 2002 16:14:29 -0800
> OK. I think in your case it's probably harmless. I thought
> that two (order 1) 4K pages can hold 2000 4 byte group IDs,
> and that "ought to be enough for anybody". If you envision
> 10,000 groups, then perhaps you are right, except that it may
> be about time to think about your data structures a little more.
> I'll let Andi to remind you about the performance impact (vmalloc
> area is outside of the big TLB area).
vmalloc will allocate 12K of address space or so and will actually die
first with fragmentation problems. We should also keep small numbers of
groups inline otherwise you are going to upset the "million threads"
people 8)
next prev parent reply other threads:[~2002-11-15 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1037316781.6599.linux-kernel2news@redhat.com>
2002-11-15 0:06 ` Pete Zaitcev
2002-11-15 0:14 ` Tim Hockin
2002-11-15 0:31 ` Pete Zaitcev
2002-11-15 0:46 ` Tim Hockin
2002-11-15 1:19 ` William Lee Irwin III
2002-11-15 1:45 ` Pete Zaitcev
2002-11-15 1:53 ` William Lee Irwin III
[not found] ` <3DD44742.2DFE4407@digeo.com>
2002-11-15 1:24 ` Tim Hockin
2002-11-15 1:30 ` Andrew Morton
2002-11-15 2:33 ` Tim Hockin
2002-11-15 2:41 ` Andrew Morton
2002-11-15 15:13 ` Alan Cox
2002-11-15 6:00 ` Aaron Lehmann
2002-11-15 1:04 ` Alan Cox [this message]
2002-11-15 13:32 ` Frank van Maarseveen
2002-11-14 23:26 Timothy Hockin
2002-11-15 16:30 ` Horst von Brand
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=1037322253.17766.3.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®