Re: [PATCH-v2] target/iblock: Convert WRITE_SAME to blkdev_issue_zeroout

Nicholas, > 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 COMPARE_AND_WRITE primitives. > > In practice though I've not seen any users of IBLOCK WRITE_SAME for > anything other than VAAI

Re: [PATCH-v2] target/iblock: Convert WRITE_SAME to blkdev_issue_zeroout

Nicholas, > 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 COMPARE_AND_WRITE primitives. > > In practice though I've not seen any users of IBLOCK WRITE_SAME for > anything other than VAAI

[PATCH-v2] target/iblock: Convert WRITE_SAME to blkdev_issue_zeroout

From: Nicholas Bellinger 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 COMPARE_AND_WRITE primitives. In practice though I've not seen any users of IBLOCK WRITE_SAME

[PATCH-v2] target/iblock: Convert WRITE_SAME to blkdev_issue_zeroout

From: Nicholas Bellinger 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 COMPARE_AND_WRITE primitives. In practice though I've not seen any users of IBLOCK WRITE_SAME for anything other than