From: Ingo Oeser <ioe-lkml@rameria.de>
To: Mike Waychison <Michael.Waychison@Sun.COM>
Cc: linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>,
linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>,
linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>,
linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [NFS] RE: [autofs] multiple servers per automount
Date: Wed, 15 Oct 2003 12:28:02 +0200 [thread overview]
Message-ID: <200310151228.02741.ioe-lkml@rameria.de> (raw)
In-Reply-To: <3F8C82EF.2010104@sun.com>
On Wednesday 15 October 2003 01:12, Mike Waychison wrote:
> The problem still remains in 2.6 that we limit the count to 256. I've
> attached a quick patch that I've compiled and tested. I don't know if
> there is a better way to handle dynamic assignment of minors (haven't
> kept up to date in that realm), but if there is, then we should probably
> use it instead.
In your patch you allocate inside the spinlock.
I would suggest to do sth. like the following:
void *local;
if (!unamed_dev_inuse) {
local = get_zeroed_page(GFP_KERNEL);
if (!local)
return -ENOMEM;
}
spinlock(&unamed_dev_lock);
mb();
if (!unamed_dev_inuse) {
unamed_dev_inuse = local;
/* Used globally, don't free now */
local = NULL;
}
/*
Do the lookup and alloc
*/
spinunlock(&unamed_dev_lock);
/* Free page, because of race on allocation. */
if (local)
free_page(local);
Which will swap the pointers atomically and still alloc outside the
non-sleeping locking.
Regards
Ingo Oeser
next prev parent reply other threads:[~2003-10-15 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0310142131090.3044-100000@raven.themaw.net>
2003-10-14 15:52 ` Mike Waychison
2003-10-14 20:44 ` H. Peter Anvin
2003-10-14 23:12 ` Mike Waychison
2003-10-15 10:28 ` Ingo Oeser [this message]
2003-10-15 16:16 ` Mike Waychison
2003-10-23 13:37 ` Ian Kent
2003-10-23 17:00 ` Mike Waychison
2003-10-23 17:09 ` Tim Hockin
2003-10-24 0:47 ` Ian Kent
2003-10-24 1:42 ` Tim Hockin
2003-10-15 7:22 ` Ian Kent
2003-10-15 14:31 Lever, Charles
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=200310151228.02741.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=Michael.Waychison@Sun.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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®