From: Nathan Scott <nathans@sgi.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
kenneth.w.chen@intel.com, cattelan@xfs.org, lord@xfs.org
Subject: Re: [PATCH] per-backing dev unplugging #2
Date: Fri, 12 Mar 2004 09:44:43 +1100 [thread overview]
Message-ID: <20040311224443.GC736@frodo> (raw)
In-Reply-To: <20040311083619.GH6955@suse.de>
Hi Jens,
On Thu, Mar 11, 2004 at 09:36:19AM +0100, Jens Axboe wrote:
> Hi,
>
> Final version, unless something stupid pops up. Changes:
>
> - Adapt to 2.6.4-mm1
> - Cleaned up the dm bits, much nicer with the lockless unplugging
> (thanks Joe)
> - md and loop unplugging, stacked devices should unplug their targets.
> Otherwise they'll end up waiting for the unplug timer, which sucks.
> - XFS fixed up, I hope. XFS folks still encouraged to look at this,
> looks better this time around though (and works, I tested).
...[snip]
> diff -ur -X /home/axboe/cdrom/exclude /opt/kernel/linux-2.6.4-mm1/fs/xfs/linux/xfs_buf.c linux-2.6.4-mm1/fs/xfs/linux/xfs_buf.c
> --- /opt/kernel/linux-2.6.4-mm1/fs/xfs/linux/xfs_buf.c 2004-03-11 03:55:21.000000000 +0100
> +++ linux-2.6.4-mm1/fs/xfs/linux/xfs_buf.c 2004-03-11 09:07:12.706793571 +0100
...[snip]
> @@ -1689,7 +1685,6 @@
> page_buf_t *pb;
> struct list_head *curr, *next, tmp;
> int pincount = 0;
> - int flush_cnt = 0;
>
> pagebuf_runall_queues(pagebuf_dataio_workqueue);
> pagebuf_runall_queues(pagebuf_logio_workqueue);
> @@ -1733,14 +1728,8 @@
>
> pagebuf_lock(pb);
> pagebuf_iostrategy(pb);
> - if (++flush_cnt > 32) {
> - blk_run_queues();
> - flush_cnt = 0;
> - }
> }
>
> - blk_run_queues();
> -
Extrapolating out from Steve's last comment yesterday/day before,
this final blk_run_queues removal here should be replaced with:
+ if (flags & PBDF_WAIT)
+ blk_run_address_space(target->pbr_mapping);
and we XFS guys need to huddle some more and figure out whether the
magic number used earlier there (32) and the request starvation it
was preventing, is still an issue on 2.6.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-03-11 22:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 8:36 [PATCH] per-backing dev unplugging #2 Jens Axboe
2004-03-11 22:44 ` Nathan Scott [this message]
2004-03-12 1:23 ` William Lee Irwin III
2004-03-12 6:41 ` Ingo Oeser
2004-03-12 8:04 ` Jens Axboe
2004-03-12 19:51 ` Chris Mason
2004-03-12 20:03 ` Andrew Morton
2004-03-12 20:02 ` Jens Axboe
2004-03-12 20:34 ` Chris Mason
2004-03-12 20:34 ` Jens Axboe
2004-03-12 20:41 ` Chris Mason
2004-03-12 20:51 ` Jens Axboe
2004-03-14 20:43 ` Chris Mason
2004-03-14 20:47 ` Jens Axboe
2004-03-14 20:57 ` Chris Mason
2004-03-14 21:04 ` Andrew Morton
2004-03-14 21:09 ` Jens Axboe
2004-03-15 21:58 ` Chris Mason
2004-03-12 20:06 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 5:22 Jeremy Higdon
2004-03-16 6:36 ` Nick Piggin
2004-03-16 7:20 ` Jeremy Higdon
2004-03-16 7:38 ` Jens Axboe
2004-03-17 0:23 ` Jeremy Higdon
2004-03-16 7:46 ` Nick Piggin
2004-03-16 7:29 ` Jens Axboe
2004-03-16 17:20 ` Jesse Barnes
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=20040311224443.GC736@frodo \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=cattelan@xfs.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.org \
/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.