From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: I/O path cleanup
Date: Tue, 30 Sep 2014 15:31:25 +0200 [thread overview]
Message-ID: <542AB0AD.1090604@acm.org> (raw)
In-Reply-To: <20140908151301.GA2551@lst.de>
On 09/08/14 17:13, Christoph Hellwig wrote:
> On Mon, Sep 08, 2014 at 09:22:40AM +0200, Bart Van Assche wrote:
>> On 09/07/14 18:31, Christoph Hellwig wrote:
>>> This series cleans up a couple of lose ends I noticed during the scsi-mq
>>> work, but which weren't important enough to address during the last cycle.
>>
>> Is there perhaps a public git tree available with this patch series ? I
>> have tried to apply these patches on top of v3.17-rc4 but unfortunately
>> without success:
>
> I've pushed a scsi-io-path-cleanups tree to my scsi-queue.git tree.
>
> I think you were missing the patches from the core-for-3.18 branch which
> overlap a bit.
>
> I will also rebase the core-for-3.18 and drivers-for-18 branches soon
> as -rc1 which they are currently based on has the percpu issues the
> scsi + blk-mq can trigger easily.
(replying to an e-mail of three weeks ago)
Hello Christoph,
At least in the tests I ran myself these patches are working fine in
combination with scsi-mq and the SRP initiator. The tree I have been
testing with has commit ID ec8af1eb08f2 - this is the tree on top of
v3.17-rc4.
Bart.
next prev parent reply other threads:[~2014-09-30 13:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 16:31 I/O path cleanup Christoph Hellwig
2014-09-07 16:31 ` [PATCH 1/8] scsi: don't use scsi_next_command in scsi_reset_provider Christoph Hellwig
2014-10-01 12:03 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 2/8] scsi: remove scsi_next_command Christoph Hellwig
2014-10-01 12:06 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 3/8] scsi: clean up S/G table freeing Christoph Hellwig
2014-10-01 12:22 ` Bart Van Assche
2014-10-01 21:05 ` Christoph Hellwig
2014-09-07 16:31 ` [PATCH 4/8] scsi: stop passing a gfp_mask argument down the command setup path Christoph Hellwig
2014-10-01 12:28 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 5/8] scsi: move scsi_dispatch_cmd to scsi_lib.c Christoph Hellwig
2014-10-01 12:30 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 6/8] scsi: move more requeue handling into scsi_requeue_command Christoph Hellwig
2014-10-01 12:33 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 7/8] scsi: split error handling slow path out of scsi_io_completion Christoph Hellwig
2014-10-01 12:46 ` Bart Van Assche
2014-09-07 16:31 ` [PATCH 8/8] scsi: merge scsi_finish_command and scsi_io_completion Christoph Hellwig
2014-10-01 12:55 ` Bart Van Assche
2014-09-08 7:22 ` I/O path cleanup Bart Van Assche
2014-09-08 15:13 ` Christoph Hellwig
2014-09-30 13:31 ` Bart Van Assche [this message]
2014-09-30 13:43 ` Christoph Hellwig
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=542AB0AD.1090604@acm.org \
--to=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.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.