From: Christoph Hellwig <hch@lst.de>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] Use REQ_OP_WRITE_SAME to implement WRITE SAME
Date: Tue, 02 Jul 2019 16:26:19 +0000 [thread overview]
Message-ID: <20190702162619.GA19142@lst.de> (raw)
In-Reply-To: <20190702153031.3832-1-bvanassche@acm.org>
I actually rather wanted to get rid of REQ_OP_WRITE_SAME entirely.
Do you have a use case for this?
Note that it isn't going to help with nvme either, as there is no
write same command in nvme.
next prev parent reply other threads:[~2019-07-02 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 15:30 [PATCH 0/2] Use REQ_OP_WRITE_SAME to implement WRITE SAME Bart Van Assche
2019-07-02 16:26 ` Christoph Hellwig [this message]
2019-07-02 17:15 ` Bart Van Assche
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=20190702162619.GA19142@lst.de \
--to=hch@lst.de \
--cc=target-devel@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.