From: Pete Zaitcev <zaitcev@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Tim Hockin <thockin@hockin.org>,
Linus Torvalds <torvalds@osdl.org>,
Pete Zaitcev <zaitcev@redhat.com>,
braam@clusterfs.com,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Many groups patch.
Date: Wed, 1 Oct 2003 22:46:36 -0400 [thread overview]
Message-ID: <20031001224636.A21298@devserv.devel.redhat.com> (raw)
In-Reply-To: <20031002022545.7D49D2C14D@lists.samba.org>; from rusty@rustcorp.com.au on Thu, Oct 02, 2003 at 12:25:10PM +1000
> > Groups are sorted and b-searched for efficiency.
>
> That's where I feel Linus' comment about catering to stupidity comes
> in 8)
I'm in this discussion for NFS groups only. The difficulty
is that NFS needs to sort groups differently, LRU by usage
(instead of numerical value). Therefore, two ways to index
that data set are unavoidable. Two b-trees, perhaps.
-- Pete
next prev parent reply other threads:[~2003-10-02 2:46 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
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 [this message]
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=20031001224636.A21298@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=braam@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=thockin@hockin.org \
--cc=torvalds@osdl.org \
/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