From: Lou Langholtz <ldl@aros.net>
To: Paul.Clements@steeleye.com
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [RFC][PATCH] nbd driver for 2.5+: fix locking issues with ioctl UI
Date: Wed, 25 Jun 2003 13:41:00 -0600 [thread overview]
Message-ID: <3EF9FACC.80503@aros.net> (raw)
In-Reply-To: <3EF9F094.3030506@aros.net>
Lou Langholtz wrote:
> . . . On the other hand I've been thinking that I might be able to
> take advantage of the irq locked condition imposed by the
> q->queue_lock and just use nbd_lock to replace q->queue_lock then. Al
> and Andrew seem to have a much deeper understanding though for
> spinlocking though so I'll defer to there comments on this idea (of
> replacing lo->queue_lock by use of nbd_lock). This has the added
> attraction of already having nbd_lock locked when in do_nbd_request.. . .
Typo! Above should have read "just use nbd_lock to replace
lo->queue_lock" (another spinlock_t per nbd_device). Anyways... would
using the one nbd_lock to also protect the lo->queue_list work better
than using the queue_lock per nbd_device I'm wondering. According to the
prior discusions about spinlocks this should be better. I don't have a
picture right now of wether that even works or not. Gotta run though,
thanks!
next prev parent reply other threads:[~2003-06-25 19:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 6:51 [RFC][PATCH] nbd driver for 2.5+: fix locking issues with ioctl UI Lou Langholtz
2003-06-25 7:19 ` Andrew Morton
2003-06-25 14:24 ` Lou Langholtz
2003-06-25 15:36 ` Lou Langholtz
2003-06-25 15:55 ` Christoph Hellwig
2003-06-25 17:38 ` Lou Langholtz
2003-06-25 17:44 ` Christoph Hellwig
2003-06-25 18:16 ` Lou Langholtz
2003-06-25 18:19 ` Christoph Hellwig
2003-06-25 17:58 ` Anyone for NBD maintainer [was Re: [RFC][PATCH] nbd driver for 2.5+: fix locking issues with ioctl UI] Pavel Machek
2003-06-25 18:21 ` Lou Langholtz
2003-06-25 18:30 ` Pavel Machek
2003-06-25 21:35 ` Lou Langholtz
[not found] ` <Pine.LNX.4.10.10306251645580.11076-100000@clements.sc.steeleye.com>
2003-06-25 21:09 ` NBD maintainer change [was Re: Anyone for NBD maintainer] Pavel Machek
2003-06-25 17:48 ` [RFC][PATCH] nbd driver for 2.5+: fix locking issues with ioctl UI Paul Clements
2003-06-25 17:56 ` viro
2003-06-25 18:57 ` Lou Langholtz
2003-06-25 19:41 ` Lou Langholtz [this message]
2003-06-25 20:00 ` Paul Clements
2003-06-25 22:17 ` Lou Langholtz
2003-06-28 17:13 ` Paul Clements
2003-06-30 16:10 ` Lou Langholtz
2003-06-28 17:20 ` [PATCH] nbd: maintain compatibility with existing nbd tools Paul Clements
2003-06-29 18:42 ` Pavel Machek
2003-06-29 21:04 ` [PATCH 2.5.73] " Paul Clements
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=3EF9FACC.80503@aros.net \
--to=ldl@aros.net \
--cc=Paul.Clements@steeleye.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--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