Re: configurable discard parameters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



By the way do you think it could be a bug of libata's SATL anyway?
Like perhaps it should break a single unmap request to multiple ATA
commands? I am not totally sure about it but it looks like there's a
limit of addressed blocks in a single ATA DSM/TRIM command (4 bytes,
which is 65535).

On 21 June 2015 at 15:03, Tom Yan <tom.ty89@xxxxxxxxx> wrote:
> On 21 June 2015 at 08:20, Martin K. Petersen <martin.petersen@xxxxxxxxxx> wrote:
>> It is a SATA-attached drive, it has no block limits VPD. What you are
>> seeing is information prepared by libata's SATL.
>>
>> Because if the vendor got these trivial values wrong there is little to
>> no chance that they implemented discard correctly in their firmware.
>
> I don't get it. So there's a chance that the VPDs is not purely from
> the hardware? Then how can I differentiate them? But then you said
> "the vendor got these trivial values wrong", so were you talking about
> this drive or just for real SCSI drives?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux