Re: [PATCH 2/8] target: remove iblock WRITE_SAME passthrough support

2017-11-14 Thread Bryant G. Ly
On 4/12/17 12:30 AM, Nicholas A. Bellinger wrote: > On Mon, 2017-04-10 at 18:08 +0200, Christoph Hellwig wrote: >> Use the pscsi driver to support arbitrary command passthrough >> instead. >> > The people who are actively using iblock_execute_write_same_direct() are > doing so in the context of

Re: [PATCH 2/8] target: remove iblock WRITE_SAME passthrough support

2017-06-01 Thread Christoph Hellwig
On Wed, May 31, 2017 at 11:27:01PM -0700, Nicholas A. Bellinger wrote: > Hey HCH & Jens, > > Is this already queued up for v4.13 to address the missing LBPRZ feature > bit..? > > If not, I'll happy to take it via target-pending along with the > following to re-enable it via

Re: [PATCH 2/8] target: remove iblock WRITE_SAME passthrough support

2017-06-01 Thread Nicholas A. Bellinger
Hey HCH & Jens, Is this already queued up for v4.13 to address the missing LBPRZ feature bit..? If not, I'll happy to take it via target-pending along with the following to re-enable it via max_write_zeroes_sectors. diff --git a/drivers/target/target_core_device.c

Re: [PATCH 2/8] target: remove iblock WRITE_SAME passthrough support

2017-04-11 Thread Christoph Hellwig
Hi Nic, this patch looks fine, and I'll include it for the next post. I'll move some of the explanation in this mail into the patch, though.

Re: [PATCH 2/8] target: remove iblock WRITE_SAME passthrough support

2017-04-11 Thread Nicholas A. Bellinger
On Mon, 2017-04-10 at 18:08 +0200, Christoph Hellwig wrote: > Use the pscsi driver to support arbitrary command passthrough > instead. > The people who are actively using iblock_execute_write_same_direct() are doing so in the context of ESX VAAI BlockZero, together with EXTENDED_COPY and