From: David Mosberger <davidm@napali.hpl.hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: akpm@zip.com.au, neilb@cse.unsw.edu.au, braam@clusterfs.com,
davem@redhat.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
David Mosberger-Tang <davidm@HPL.HP.COM>,
tridge@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl-controlled number of groups.
Date: Wed, 24 Sep 2003 21:19:39 -0700 [thread overview]
Message-ID: <16242.27867.715648.392875@napali.hpl.hp.com> (raw)
In-Reply-To: <20030925035943.AE41C2C04B@lists.samba.org>
>From the ia64-side, it looks mostly fine to me. Some minor things:
- Typo in first sentence of patch comment (can be -> to be ?)
- If I'm reading the patch right, there will be identical sys32_getgroups16()
definitions in .../ia32/sys_ia32.c and and compat_linux.c; did you mean
to name the latter compat_getgroups16()? (ditto for setgroups16 and s390
and sparc64, i think)
- I suspect removing NGROUPS from param.h will break glibc and/or user-level
apps. param.h is one of those kernel files that are directly exposed
to user-level; may want to keep NGROUPS inside an #ifndef __KERNEL__.
--david
>>>>> On Thu, 25 Sep 2003 13:21:01 +1000, Rusty Russell <rusty@rustcorp.com.au> said:
Rusty> We have a client (using SAMBA) who has people in 190 groups. Since NT
Rusty> has hierarchical groups, this is not all that rare.
Rusty> What do people think of this patch?
Rusty> Name: Dynamic Allocation of Groups Array When Required: With Refcounting
Rusty> Author: Rusty Russell
Rusty> Status: Tested on 2.6.0-test5-bk5
Rusty> Depends: Misc/qemu-page-offset.patch.gz
Rusty> D: This patch allows the maximum number of groups can be varied using
Rusty> D: sysctl. To do this, we use a separate group allocation if >
Rusty> D: NGROUPS_INTERNAL, which we reference count (sharing being
Rusty> D: v. v. common).
Rusty> D:
Rusty> D: Changes:
Rusty> D: 1) Remove the NGROUPS define from archs.
Rusty> D: 2) Fixup the few places which declare [NGROUPS] arrays on the stack.
Rusty> D: 3) The ia64, s390 and sparc64 ports have their own setgroups/getgroups
Rusty> D: implementations: unify them on the ia64 one, which calls the core
Rusty> D: functions.
Rusty> D: 4) Change the task_struct to have an [NGROUPS_INTERNAL] array and
Rusty> D: a pointer (not convinced this is worth it at all, might skip it
Rusty> D: and always use external).
Rusty> D: 5) Use a reference counted external array, fix up fork() to deal.
Rusty> D: 6) Introduce max_groups and use it instead of NGROUPS.
Rusty> D: 7) Add a sysctl to vary max_groups.
Rusty> D:
Rusty> D: This patch scars nfs: artificially restrict the groups there to
Rusty> D: SVC_CRED_NGROUPS (32), which is probably wrong, but won't break if
Rusty> D: they don't change the default.
Rusty> D:
Rusty> D: This patch breaks intermezzo: I'm not sure how they want to deal
Rusty> D: with it.
next prev parent reply other threads:[~2003-09-25 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 3:21 Rusty Russell
2003-09-25 4:14 ` Tim Hockin
2003-09-25 8:17 ` Rusty Russell
2003-09-25 4:19 ` David Mosberger [this message]
2003-09-25 8:08 ` Rusty Russell
2003-09-25 7:15 ` Arjan van de Ven
2003-09-25 7:25 ` William Lee Irwin III
2003-09-25 8:23 ` 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=16242.27867.715648.392875@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@zip.com.au \
--cc=braam@clusterfs.com \
--cc=davem@redhat.com \
--cc=davidm@HPL.HP.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=tridge@samba.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
all inboxes | Powered by JetHome®