From: Tommy Reynolds <reynolds@redhat.com>
To: "Jackie Meese" <jackie.m@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 32 Groups Maximum in 2.4
Date: Thu, 15 Nov 2001 09:41:16 -0600 [thread overview]
Message-ID: <20011115094116.290282cc.reynolds@redhat.com> (raw)
In-Reply-To: <3BF3DF31.4010707@vt.edu>
In-Reply-To: <3BF3DF31.4010707@vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
It was a dark and stormy night. Suddenly
"Jackie Meese" <jackie.m@vt.edu> began to type furiously:
> I've been looking for some time on how to raise the maximum number of
> groups for the 2.4 kernel. I've discovered how to do this kernel, with
> a discussion a few months ago on this
> list.http://www.cs.helsinki.fi/linux/linux-kernel/2001-13/0807.html
>
> However the follow up of "You gotta change the task struct..." means
> nothing to me.
>
> Can someone be more specific as to the changes that need to be made to
> accomplish this? Change the task struct where? I can find lots of
> references to task_struct in the sources simply by grepping them, but I
> can't since any that point to a 32 limit. I'm not a kernel hacker, but
> I've read and edited a fair bit of source code in my time, so I thik I
> just need a bit more of a clue in here.
Look at the file "include/asm-<proc>/param.h to find the symbol "NGROUPS".
Change that to whatever value you like.
The "task_struct" is the per-process descriptor. You can find it in
"/usr/src/linux/include/linux/sched.h", but you shouldn't need to change
anything there.
Once you've changed "NGROUPS", then "make clean oldconfig dep bzImage modules"
as usual. That will change the kernel's idea how how many groups you can have.
You will probably need to recompile the userland stuff, from LIBC to the shells
because "NGROUPS" can be pervasive.
Your mileage may vary.
---------------------------------------------+-----------------------------
Tommy Reynolds | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone: +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA | FAX: +1.256.837.3839
Senior Software Developer | Mobile: +1.919.641.2923
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2001-11-15 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 15:28 32 Groups Maximum in 2.4 Jackie Meese
2001-11-15 15:41 ` Tommy Reynolds [this message]
2001-11-15 16:22 ` Tim Hockin
2001-11-15 18:39 ` Andreas Dilger
2001-11-15 19:03 ` Jackie Meese
2001-11-15 18:55 ` Tim Hockin
2001-11-15 20:34 ` Andreas Dilger
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=20011115094116.290282cc.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=jackie.m@vt.edu \
--cc=linux-kernel@vger.kernel.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 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.