From: William Lee Irwin III <wli@holomorphy.com>
To: Tim Hockin <thockin@sun.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH 1/2] Remove NGROUPS hardlimit (resend w/o qsort)
Date: Thu, 14 Nov 2002 17:19:47 -0800 [thread overview]
Message-ID: <20021115011947.GP23425@holomorphy.com> (raw)
In-Reply-To: <3DD443EC.2080504@sun.com>
On Thu, Nov 14, 2002 at 04:46:36PM -0800, Tim Hockin wrote:
> Offer an alternative? :) Linked list costs us as much or MORE for
> ->next as the gid_t. kmalloc() doesn't work for previous reasoning. I
> considered a list of gid arr[256] or similar. A voice reminds me that
> it doesn't impact us noticably in real use. Now, maybe other
> architectures will find a good reason to switch to kmalloc() list of
> smaller arrays, and the associated complextities or something else more
> clever.
Well, there are always B-trees; nice low arrival rates to the allocator
owing to elements/node and O(lg(n)) searches with low constants due to
big fat branching factors. Not my call though.
Bill
next prev parent reply other threads:[~2002-11-15 1:15 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
2002-11-15 0:31 ` Pete Zaitcev
2002-11-15 0:46 ` Tim Hockin
2002-11-15 1:19 ` William Lee Irwin III [this message]
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=20021115011947.GP23425@holomorphy.com \
--to=wli@holomorphy.com \
--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 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.