All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@sun.com>
To: Pete Zaitcev <zaitcev@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH 1/2] Remove NGROUPS hardlimit (resend w/o qsort)
Date: Thu, 14 Nov 2002 16:14:29 -0800	[thread overview]
Message-ID: <3DD43C65.80103@sun.com> (raw)
In-Reply-To: 200211150006.gAF06JF01621@devserv.devel.redhat.com

Pete Zaitcev wrote:
> Two questions.
> 
> 1. Why are arrays vmalloc-ed? This is a goochism which you have
>    to justify.

Because they can be as large as root allows, and when we used kmalloc() 
it would actually fail from time to time.

> 2. How do these changes sit with LLNL's changes to increase
>    number of groups that NFS client can support? It's not
>    a showstopper, but would be nice if you two cooperated.

hmm, I haven't heard anything about them - can you offer an email or URL?

Thanks


-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Linux Kernel Engineering
thockin@sun.com


  reply	other threads:[~2002-11-15  0:07 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 ` [BK PATCH 1/2] Remove NGROUPS hardlimit (resend w/o qsort) Pete Zaitcev
2002-11-15  0:14   ` Tim Hockin [this message]
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
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=3DD43C65.80103@sun.com \
    --to=thockin@sun.com \
    --cc=linux-kernel@vger.kernel.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.