From: Jens Axboe <axboe@kernel.dk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, shli@kernel.org, snitzer@redhat.com
Subject: Re: Discard merging / Write same support v5
Date: Thu, 20 Sep 2012 14:47:17 +0200 [thread overview]
Message-ID: <505B1055.5090509@kernel.dk> (raw)
In-Reply-To: <1348145006.2936.12.camel@dabdike.int.hansenpartnership.com>
On 09/20/2012 02:43 PM, James Bottomley wrote:
> On Thu, 2012-09-20 at 14:33 +0200, Jens Axboe wrote:
>> On 09/18/2012 06:19 PM, Martin K. Petersen wrote:
>>> I've been beating on this patch kit for the last few weeks with a bunch
>>> of different devices. I have also tested extensively with Shaohua Li's
>>> MD RAID0 discard support.
>>>
>>> The only functional change is support for discard and write same
>>> bio/request merging. Other than that there were a few tweaks for later
>>> kernels by both Mike and me.
>>>
>>> I put a writesame5 branch on:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/mkp/linux.git
>>>
>>> It's against block/for-3.7/core.
>>>
>>> [PATCH 1/8] block: Clean up special command handling logic
>>> [PATCH 2/8] block: Consolidate command flag and queue limit checks
>>> [PATCH 3/8] block: Implement support for WRITE SAME
>>> [PATCH 4/8] block: Make blkdev_issue_zeroout use WRITE SAME
>>> [PATCH 5/8] block: ioctl to zero block ranges
>>> [PATCH 6/8] scsi: Add a report opcode helper
>>> [PATCH 7/8] sd: Permit merged discard requests
>>> [PATCH 8/8] sd: Implement support for WRITE SAME
>>
>> Thanks Martin, I queued up 1..5 in for-3.7/core. I'm assuming James will
>> pick up the SCSI bits?
>
> Yes, but Linus gave me a rocket about post merge trees. Can you do this
> on a separate branch and I'll build on top of that?
He did, didn't he... You could just use for-3.7/core as of today,
there's not that much in there yet. Alternatively, I'd have to rebase
for-3.7/core and rip them out, put them in a separate branch, and pull
that back into for-3.7/core.
--
Jens Axboe
prev parent reply other threads:[~2012-09-20 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 16:19 Discard merging / Write same support v5 Martin K. Petersen
2012-09-18 16:19 ` [PATCH 1/8] block: Clean up special command handling logic Martin K. Petersen
2012-09-18 16:19 ` [PATCH 2/8] block: Consolidate command flag and queue limit checks for merges Martin K. Petersen
2012-09-18 17:59 ` Mike Snitzer
2012-09-18 16:19 ` [PATCH 3/8] block: Implement support for WRITE SAME Martin K. Petersen
2012-09-18 16:19 ` [PATCH 4/8] block: Make blkdev_issue_zeroout use " Martin K. Petersen
2012-09-18 16:19 ` [PATCH 5/8] block: ioctl to zero block ranges Martin K. Petersen
2012-09-18 16:19 ` [PATCH 6/8] scsi: Add a report opcode helper Martin K. Petersen
2012-09-18 16:19 ` [PATCH 7/8] sd: Permit merged discard requests Martin K. Petersen
2012-09-20 0:35 ` Shaohua Li
2012-09-18 16:19 ` [PATCH 8/8] sd: Implement support for WRITE SAME Martin K. Petersen
2012-09-20 12:33 ` Discard merging / Write same support v5 Jens Axboe
2012-09-20 12:43 ` James Bottomley
2012-09-20 12:47 ` Jens Axboe [this message]
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=505B1055.5090509@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shli@kernel.org \
--cc=snitzer@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).