From: Tim Hockin <thockin@hockin.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Many groups patch.
Date: Mon, 29 Sep 2003 15:43:43 -0700 [thread overview]
Message-ID: <20030929154343.A13742@hockin.org> (raw)
In-Reply-To: <200309292229.h8TMTWw32486@devserv.devel.redhat.com>; from zaitcev@redhat.com on Mon, Sep 29, 2003 at 06:29:32PM -0400
On Mon, Sep 29, 2003 at 06:29:32PM -0400, Pete Zaitcev wrote:
> >> This version drops the internal groups array (it's so often shared
> >> that it's not worth it, and the logic becomes a bit neater), and does
> >> vmalloc fallback in case someone has massive number of groups.
> >
> > Why?
>
> > The vmalloc space is limited, and the code just gets uglier.
>
> Tim was going to write a version that segments groups into
> smaller arrays. I reckon it was too difficult?
I posted it once or twice then got busy. It's an array of pages. Rusty has
it, but didn't believe me when I said Linus wouldn't let vmalloc() fly.
> > Have you been looking at glibc sources lately, or why do you believe that
> > we should encourage insane usage?
>
> We have some customers who run insane number of groups,
> with their own patches. This practice is popular in the
> Beowulf crowd for some reason. I should note this is not
> very mainstream.
I'd be ok with the simplest "kmalloc or too bad" version, but our customers
wouldn't.
My version uses a struct group_info which has an array of pages. The groups
are sorted and bsearched, instead of linear. The perfomance is quite good.
An older version against 2.6.0-test1 or something is attached. If this
method will fly, I'll take some of Rusty's good ideas and finish this
version of it..
Linus?
next prev parent reply other threads:[~2003-09-29 22:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1064857032.26219.linux-kernel2news@redhat.com>
2003-09-29 22:29 ` [PATCH] Many groups patch Pete Zaitcev
2003-09-29 22:43 ` Tim Hockin [this message]
2003-09-29 22:55 ` Tim Hockin
2003-09-29 23:10 ` Linus Torvalds
2003-10-01 7:10 ` Tim Hockin
2003-10-01 18:46 ` Tim Hockin
2003-10-01 19:22 ` Linus Torvalds
2003-10-01 20:29 ` Tim Hockin
2003-10-01 20:46 ` Linus Torvalds
2003-10-01 21:12 ` Tim Hockin
2003-10-01 21:16 ` Tim Hockin
2003-10-02 1:00 ` IDEA: arch uid16 cleanup (was 'Many groups patch') Tim Hockin
2003-10-02 2:09 ` [PATCH] Many groups patch Rusty Russell
2003-10-02 4:39 ` Tim Hockin
2003-10-02 9:10 ` David S. Miller
2003-10-02 2:25 ` Rusty Russell
2003-10-02 2:46 ` Pete Zaitcev
2003-09-29 7:19 Rusty Russell
2003-09-29 17:25 ` Linus Torvalds
2003-09-29 23:30 ` Rusty Russell
2003-09-30 4:11 ` Tim Hockin
2003-10-01 7:29 ` Rusty Russell
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=20030929154343.A13742@hockin.org \
--to=thockin@hockin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.