Re: Bigger discard payloads

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

 



On 10-11-25 09:43 PM, Martin K. Petersen wrote:

I posted the first version of this patch a few months ago. Inspired by
the recent discussions I decided to take another stab at supporting TRIM
payloads bigger than 512 bytes.

Most of the drives I have here advertise max payload of 512 bytes.

Given this, and that the kernel won't actually use more than one range today
(except for sequential/adjacent ranges), do we think that supporting
more than 512 bytes will be useful?

I suppose it could be useful once we get multiple non-adjacent range support.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux