All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Tim Hockin <thockin@sun.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH 1/4] fix NGROUPS hard limit (resend)
Date: Tue, 22 Oct 2002 13:03:47 -0500	[thread overview]
Message-ID: <200210221303.47488.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <3DB58CBD.3030207@sun.com>

On Tuesday 22 October 2002 12:37 pm, Tim Hockin wrote:
> Alan Cox wrote:
> > On Tue, 2002-10-22 at 18:26, Tim Hockin wrote:
> >>Alan Cox wrote:
> >>>Ok sanity check time. Why do you need qsort and bsearch for this kind of
> >>>thing. Just how many groups do you plan to support ?
> >>
> >>Unlimited - we've tested with tens of thousands.
> >
> > Now how about the real world requirements ?
>
> Those were real world requirements - we got the number 10,000 from our
> product management, which (presumably) spoke with customers.  On the
> hosting systems, it is really possible to have thousands of virtual sites.
>
> Now, I don't much care if you want it to be a linear search, and I'll
> revert it, if needed, but qsort() is already in in XFS specific code,
> and bsearch is small.  It doesn't negatively impact any fast path, and
> provides better behavior for the crazies that really want 10,000 groups.
>
> Tim

Does it actually work with NFS???? or any networked file system?
Most of them limit ngroups to 16 to 32, and cannot send any data
if there is an overflow, since that overflow would replace all of the
data you try to send/recieve...

And I really doubt that anybody has 10000 unique groups (or even
close to that) running under any system. The center I'm at has
some of the largest UNIX systems ever made, and there are only
about 600 unique groups over the entire center. The largest number
of groups a user can be in is 32. And nobody even comes close.
-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

  reply	other threads:[~2002-10-22 18:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  0:36 [BK PATCH 1/4] fix NGROUPS hard limit (resend) Timothy Hockin
2002-10-22  1:39 ` Aaron Lehmann
2002-10-22 17:44   ` Tim Hockin
2002-10-22  9:51 ` Alan Cox
2002-10-22 17:26   ` Tim Hockin
2002-10-22 17:45     ` Alan Cox
2002-10-22 17:37       ` Tim Hockin
2002-10-22 18:03         ` Jesse Pollard [this message]
2002-10-22 18:21           ` Tim Hockin
2002-10-22 18:54             ` Rik van Riel
2002-10-22 19:12             ` Jesse Pollard
2002-10-22 19:39               ` Rik van Riel
2002-10-25  9:34             ` Panu Matilainen
2002-10-25 12:49               ` jw schultz
2002-10-25 18:17                 ` Tim Hockin
2002-10-22 19:45           ` Mike Touloumtzis
2002-10-22 20:13             ` Jesse Pollard
2002-10-22 20:30               ` Mike Touloumtzis
2002-10-23 14:17                 ` Jesse Pollard
2002-10-22 20:18           ` Hildo.Biersma
2002-10-23  2:41           ` Simon Kirby
     [not found] <354127220@toto.iv>
2002-10-23  0:09 ` Peter Chubb
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23 10:16 Randal, Phil
2002-10-29 19:32 Timothy Hockin

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=200210221303.47488.pollard@admin.navo.hpc.mil \
    --to=pollard@admin.navo.hpc.mil \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@sun.com \
    --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 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.