From: Mike Waychison <Michael.Waychison@Sun.COM>
To: raven@themaw.net
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Maneesh Soni <maneesh@in.ibm.com>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 4/8] autofs4-2.6 - to support autofs 4.1.x
Date: Wed, 28 Jan 2004 12:04:34 -0500 [thread overview]
Message-ID: <4017EBA2.1080302@sun.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401282321530.17471@raven.themaw.net>
raven@themaw.net wrote:
>
>Patch:
>
>4-autofs4-2.6.0-test9-waitq2.patch
>
>Adds a spin lock to serialize access to wait queue in the super block info
>struct.
>
>
>
A while back I wrote up a patch for autofs3 that serialized waitq access
and changed the waitq counters to atomic_t. I never sent it out because
I had realized that the changes I made weren't needed as all waitq
code-paths were running under the BKL (the big ones were ->lookup and
the ioctls).
Looking briefly at autofs4, this appears to be the case as well, so this
serializing probably isn't needed as long as care is made not block
while walking the list.
--
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2004-01-28 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 15:39 [PATCH 4/8] autofs4-2.6 - to support autofs 4.1.x raven
2004-01-28 17:04 ` Mike Waychison [this message]
2004-01-29 0:35 ` Ian Kent
2004-01-29 1:27 ` Mike Waychison
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=4017EBA2.1080302@sun.com \
--to=michael.waychison@sun.com \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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