Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1412720 > unrolled thread
| Started by | "Martin K. Petersen" <martin.petersen@oracle.com> |
|---|---|
| First post | 2016-06-03 05:00 +0200 |
| Last post | 2016-06-03 05:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] block: correctly fallback for zeroout "Martin K. Petersen" <martin.petersen@oracle.com> - 2016-06-03 05:00 +0200
| From | "Martin K. Petersen" <martin.petersen@oracle.com> |
|---|---|
| Date | 2016-06-03 05:00 +0200 |
| Subject | Re: [PATCH] block: correctly fallback for zeroout |
| Message-ID | <rFNv4-5UF-1@gated-at.bofh.it> |
>>>>> "Sitsofe" == Sitsofe Wheeler <sitsofe@yahoo.com> writes: Sitsofe> The original SCSI WRITE SAME has overloaded semantics - not Sitsofe> only does it mean "write this data multiple times" but it can Sitsofe> also be used to mean "discard this range" too. If the kernel's Sitsofe> command was modelled on the SCSI original perhaps this Sitsofe> conflation clouded things? REQ_WRITE_SAME in the context of the kernel explicitly means "write payload to this block range". A REQ_DISCARD command may be serviced using WRITE SAME(16) with the UNMAP bit set in the SCSI disk driver but that's entirely orthogonal. -- Martin K. Petersen Oracle Linux Engineering
Back to top | Article view | linux.kernel
csiph-web