public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tim Hockin <thockin@hockin.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com,
	braam@clusterfs.com, neilb@cse.unsw.edu.au,
	David Meybohm <dmeybohm@bellsouth.net>,
	sfr@canb.auug.org.au
Subject: Re: [PATCH] Many groups patch.
Date: Wed, 01 Oct 2003 17:29:14 +1000	[thread overview]
Message-ID: <20031001074726.A84702C0C0@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 29 Sep 2003 21:11:55 MST." <20030929211155.A28089@hockin.org>

In message <20030929211155.A28089@hockin.org> you write:
> On Tue, Sep 30, 2003 at 09:30:07AM +1000, Rusty Russell wrote:
> > > Why?
> > 
> > (Rusty points at Tim).
> > 
> > He has 10,000 groups.  Now me, I'm happy with the minimal fix.
> 
> I'm going to merge your thoughts and mine tomorrow and send it out.  Linus
> suggested the array of pages approah is more sane, so I'm going to try for
> it.  I'm going to comb through the diffs between your patch and mine.

Keeping the groups array as an array is a feature.  IMHO, if there are
too many for a kmalloc, vmalloc fallback makes sense: it's
conceptually simple and not that much code.

Introducing an almost-vmalloc because Linus didn't like the vmalloc
just doesn't make sense, IMHO.

> > And worse, there are the intermediate kmallocs which would need to be
> > fixed (thanks to Stephen Rothwell for pointing this out).  Fixing this
> > would make it even uglier.
> 
> Specifically?  I think my patch gets all of those.  At least all the ones I
> found.

Yep, you got them, I didn't.  I am still hoping Stephen (CC'd) will
move the IA64, S390 and Sparc64 code into kernel/compat.c which will
shrink out patches.

> > Here's an updated one (with David Meybohm's fix, too -- Thanks!),
> > Rusty.
> 
> Can you elaborate on what this extra fix is?

I screwed up a free.

Cheers,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-10-01  7:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29  7:19 [PATCH] Many groups patch 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 [this message]
     [not found] <mailman.1064857032.26219.linux-kernel2news@redhat.com>
2003-09-29 22:29 ` Pete Zaitcev
2003-09-29 22:43   ` Tim Hockin
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  2:09               ` 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

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=20031001074726.A84702C0C0@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=braam@clusterfs.com \
    --cc=dmeybohm@bellsouth.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=sfr@canb.auug.org.au \
    --cc=thockin@hockin.org \
    --cc=torvalds@osdl.org \
    --cc=torvalds@transmeta.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