From: axboe@fb.com (Jens Axboe)
Subject: [PATCH v2 0/4] rewrites discard support
Date: Tue, 22 Mar 2016 14:50:35 -0600 [thread overview]
Message-ID: <56F1B01B.6030400@fb.com> (raw)
In-Reply-To: <1458631486-14120-1-git-send-email-mlin@kernel.org>
On 03/22/2016 01:24 AM, Ming Lin wrote:
> From: Ming Lin <ming.l at ssi.samsung.com>
>
> This rewrites nvme_setup_discard() with blk_add_request_payload().
> And moves it to common code so fabrics driver can also use it.
>
> v2:
> - add helper nvme_map_len()
> - allocates only 16 bytes for discard payload
> - moves command setup to common helper nvme_setup_cmd()
> - returns BLK_MQ_RQ_QUEUE_BUSY when out of memory
>
> Ming Lin (4):
> nvme: add helper nvme_map_len()
> block: add offset in blk_add_request_payload()
> nvme: rewrite discard support
> nvme: add helper nvme_setup_cmd()
>
> block/blk-core.c | 5 ++-
> drivers/block/skd_main.c | 2 +-
> drivers/nvme/host/core.c | 105 +++++++++++++++++++++++++++++++++++++++++++++++
> drivers/nvme/host/nvme.h | 55 ++++---------------------
> drivers/nvme/host/pci.c | 68 +++++++-----------------------
> drivers/scsi/sd.c | 2 +-
> include/linux/blkdev.h | 2 +-
> 7 files changed, 133 insertions(+), 106 deletions(-)
Looks good to me, I'll queue it up for 4.7. Thanks.
--
Jens Axboe
prev parent reply other threads:[~2016-03-22 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:24 [PATCH v2 0/4] rewrites discard support Ming Lin
2016-03-22 7:24 ` [PATCH v2 1/4] nvme: add helper nvme_map_len() Ming Lin
2016-03-22 7:31 ` Christoph Hellwig
2016-03-22 7:24 ` [PATCH v2 2/4] block: add offset in blk_add_request_payload() Ming Lin
2016-03-22 7:31 ` Christoph Hellwig
2016-03-22 7:24 ` [PATCH v2 3/4] nvme: rewrite discard support Ming Lin
2016-03-22 7:37 ` Christoph Hellwig
2016-03-22 7:24 ` [PATCH v2 4/4] nvme: add helper nvme_setup_cmd() Ming Lin
2016-03-22 7:38 ` Christoph Hellwig
2016-03-22 20:40 ` [PATCH v2 0/4] rewrites discard support Keith Busch
2016-03-22 20:50 ` 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=56F1B01B.6030400@fb.com \
--to=axboe@fb.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