From: Pete Zaitcev <zaitcev@redhat.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Rainer Krienke <krienke@uni-koblenz.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.17:Increase number of anonymous filesystems beyond 256?
Date: Fri, 25 Jan 2002 13:42:48 -0500 [thread overview]
Message-ID: <20020125134248.B16106@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1011275640.16596.linux-kernel2news@redhat.com> <200201240858.g0O8wnH03603@bliss.uni-koblenz.de> <20020124121649.A7722@devserv.devel.redhat.com> <200201250728.g0P7SDH26738@bliss.uni-koblenz.de> <20020125124110.A357@devserv.devel.redhat.com> <200201251834.g0PIYxj02545@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201251834.g0PIYxj02545@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Fri, Jan 25, 2002 at 11:34:59AM -0700
> Date: Fri, 25 Jan 2002 11:34:59 -0700
> From: Richard Gooch <rgooch@ras.ucalgary.ca>
> The allocation function should be safe, since it only gives majors
> which are not assigned in devices.txt. [...]
Oh, that changes it, I should have looked closer.
I am not sure the "1200 NFS mounts" case warrants the
change though, so far we have only one active user (Rainer) :)
If ISPs and universities clamour for my patch, then sure,
we may improve it with devfs_alloc_major() in 2.4, too.
Otherwise, whatever... Thanks for the explanation, Richard,
I'll keep it in my notes.
-- Pete
next prev parent reply other threads:[~2002-01-25 18:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1011275640.16596.linux-kernel2news@redhat.com>
2002-01-17 18:55 ` 2.4.17:Increase number of anonymous filesystems beyond 256? Pete Zaitcev
2002-01-18 12:12 ` Rainer Krienke
2002-01-18 19:40 ` H. Peter Anvin
2002-01-20 10:33 ` Rainer krienke
2002-01-20 10:37 ` H. Peter Anvin
2002-01-18 20:33 ` Horst von Brand
2002-01-19 22:07 ` H. Peter Anvin
2002-01-21 22:54 ` Pete Zaitcev
2002-01-18 12:26 ` Trond Myklebust
2002-01-21 12:40 ` Rainer Krienke
2002-01-22 10:25 ` Rainer Krienke
2002-01-22 10:40 ` Trond Myklebust
2002-01-22 13:08 ` Rainer Krienke
2002-01-22 13:28 ` Trond Myklebust
2002-01-22 15:23 ` Rainer Krienke
2002-01-22 15:40 ` Trond Myklebust
2002-01-22 17:45 ` Pete Zaitcev
2002-01-24 8:58 ` Rainer Krienke
2002-01-24 17:16 ` Pete Zaitcev
2002-01-24 17:29 ` Richard Gooch
2002-01-25 7:28 ` Rainer Krienke
2002-01-25 17:41 ` Pete Zaitcev
2002-01-25 18:34 ` Richard Gooch
2002-01-25 18:42 ` Pete Zaitcev [this message]
2002-01-22 19:45 ` Pete Zaitcev
[not found] <200201171351.g0HDpdK05456@bliss.uni-koblenz.de.suse.lists.linux.kernel>
2002-01-17 17:49 ` Andi Kleen
2002-01-17 13:51 Rainer Krienke
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=20020125134248.B16106@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=krienke@uni-koblenz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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