From: Jens Axboe <axboe@suse.de>
To: Steve Whitehouse <Steve@ChyGwyn.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
pavel@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: NBD Cleanup patch and bugfix in ll_rw_blk.c
Date: Wed, 28 Feb 2001 22:37:36 +0100 [thread overview]
Message-ID: <20010228223736.P21518@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10102281138470.5932-100000@penguin.transmeta.com> <200102282127.VAA20600@gw.chygwyn.com>
In-Reply-To: <200102282127.VAA20600@gw.chygwyn.com>; from steve@gw.chygwyn.com on Wed, Feb 28, 2001 at 09:27:39PM +0000
On Wed, Feb 28 2001, Steve Whitehouse wrote:
> > > The bug fix in ll_rw_blk.c prevents hangs when using block devices which
> > > don't have plugging functions,
> >
> > I'm convinced that the right fix is to just make everybody have plugging
> > functions.
> >
> I'm working on that. Once I've discovered why enabling plugging causes nbd
> to hang, then I'll send a patch assuming nobody beats me to it :-)
Does anyone actually know why? Pavel didn't seem to, so maybe it
was just disabled on a hunch?
> I tested the patch with a printk() which printed whenever the new call to the
> request function was triggered. It didn't happen once in normal fs use
> with ext2 on a scsi disk. From the code I think its not even possible for
> this to be called at all for a device which has plugging. For a plugged
> device when I/O comes in, there appear to be only two cases:
>
> - Device queue empty. Device gets plugged. New request_fn call not called
> - Device queue not empty. New I/O added to back of queue. New request_fn
> not called (it only gets called when the I/O is added to the front of
> the queue).
Exactly right.
> I think nbd is the only device which doesn't use plugging at the
> moment (from a quick grep of the kernel source),
Probably right -- loop used to disable plugging to disallow merging
and tq_disk deadlocks, but now (-ac) it's a make_request style
driver instead.
--
Jens Axboe
next prev parent reply other threads:[~2001-02-28 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 19:57 NBD Cleanup patch and bugfix in ll_rw_blk.c Steve Whitehouse
2001-02-25 20:55 ` Andrea Arcangeli
2001-02-25 20:59 ` Jens Axboe
2001-02-25 22:39 ` Russell King
2001-02-25 22:49 ` Jens Axboe
2001-02-25 23:02 ` Steve Whitehouse
2001-02-28 19:41 ` Linus Torvalds
2001-02-28 21:27 ` Steve Whitehouse
2001-02-28 21:37 ` Jens Axboe [this message]
2001-02-28 23:29 ` Linus Torvalds
2001-03-01 0:07 ` Jens Axboe
2001-03-01 3:14 ` Linus Torvalds
[not found] ` <200103010314.TAA06827@penguin.transmeta.com>
2001-03-01 13:39 ` Jens Axboe
2001-03-01 14:49 ` Jens Axboe
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=20010228223736.P21518@suse.de \
--to=axboe@suse.de \
--cc=Steve@ChyGwyn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/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.