From: Jens Axboe <jens.axboe@oracle.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] 4/4 block: explicit plugging
Date: Wed, 3 Jan 2007 23:29:31 +0100 [thread overview]
Message-ID: <20070103222930.GL11203@kernel.dk> (raw)
In-Reply-To: <98F3657447CE934E9ADA3A348D854FB602858A4F@scsmsx414.amr.corp.intel.com>
On Wed, Jan 03 2007, Chen, Kenneth W wrote:
> Jens Axboe wrote on Wednesday, January 03, 2007 12:22 AM
> > > Do you have any benchmarks which got faster with these changes?
> >
> > On the hardware I have immediately available, I see no regressions wrt
> > performance. With instrumentation it's simple to demonstrate that most
> > of the queueing activity of an io heavy benchmark spends less time in
> > the kernel (most merging activity takes place outside of the queue
> lock,
> > hence queueing is lock free).
> >
> > I've asked Ken to run this series on some of his big iron, I hope
> he'll
> > have some results for us soonish.
>
> We are having some trouble with the patch set that some of our fiber
> channel
> host controller doesn't initialize properly anymore and thus lost whole
> bunch
> of disks (somewhere around 200 disks out of 900) at boot time.
> Presumably FC
> loop initialization command are done through block layer etc. I haven't
> looked into the problem closely.
>
> Jens, I assume the spin lock bug in __blk_run_queue is fixed in this
> patch
> set?
It is. Are you still seeing problems after the initial mail exchange we
had prior to christmas, or are you referencing that initial problem?
It's not likely to be a block layer issue, more likely the SCSI <->
block interactions. If you mail me a new dmesg (if your problem is with
the __blk_run_queue() fixups), I can take a look. Otherwise please do
test with the __blk_run_queue() fixup, just use the current patchset.
--
Jens Axboe
next prev parent reply other threads:[~2007-01-03 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 7:48 [BLOCK] 0/4 explicit io plugging Jens Axboe
2007-01-03 7:48 ` [PATCH] 1/4 qrcu: "quick" srcu implementation Jens Axboe
2007-01-03 7:48 ` [PATCH] 2/4 qrcu: add rcutorture test Jens Axboe
[not found] ` <1167810508576-git-send-email-jens.axboe@oracle.com>
2007-01-03 8:09 ` [PATCH] 4/4 block: explicit plugging Andrew Morton
2007-01-03 8:22 ` Jens Axboe
2007-01-03 21:50 ` Chen, Kenneth W
2007-01-03 22:29 ` Jens Axboe [this message]
2007-01-03 22:34 ` Chen, Kenneth W
2007-01-04 14:39 ` Jens Axboe
2007-01-05 22:04 ` Chen, Kenneth W
2007-01-04 4:35 ` Nick Piggin
2007-01-05 7:23 ` Jens Axboe
2007-01-03 8:31 ` [PATCH] 3/4 qrcu: add documentation Jens Axboe
2007-01-03 9:29 ` Tomas Carnecky
2007-01-03 9:39 ` Jens Axboe
2007-01-03 9:41 ` [PATCH] 4/4 block: explicit plugging 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=20070103222930.GL11203@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=npiggin@suse.de \
/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.