Re: [PATCH] blkdiscard: add new command

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

 



On Wed, Sep 26, 2012 at 10:14 PM, Lukáš Czerner <lczerner@xxxxxxxxxx> wrote:
> On Wed, 26 Sep 2012, Kay Sievers wrote:
>
>> Date: Wed, 26 Sep 2012 22:04:37 +0200
>> From: Kay Sievers <kay@xxxxxxxx>
>> To: Lukáš Czerner <lczerner@xxxxxxxxxx>
>> Cc: util-linux@xxxxxxxxxxxxxxx, kzak@xxxxxxxxxx
>> Subject: Re: [PATCH] blkdiscard: add new command
>>
>> On Wed, Sep 26, 2012 at 9:47 PM, Lukáš Czerner <lczerner@xxxxxxxxxx> wrote:
>> > On Wed, 12 Sep 2012, Lukas Czerner wrote:
>> >
>> >> Date: Wed, 12 Sep 2012 17:49:15 -0400
>> >> From: Lukas Czerner <lczerner@xxxxxxxxxx>
>> >> To: util-linux@xxxxxxxxxxxxxxx, kzak@xxxxxxxxxx
>> >> Cc: Lukas Czerner <lczerner@xxxxxxxxxx>
>> >> Subject: [PATCH] blkdiscard: add new command
>> >>
>> >> blkdiscard is used to discard device sectors. This is useful for
>> >> solid-state drivers (SSDs) and thinly-provisioned storage. Unlike
>> >> fstrim this command is used directly on the block device.
>> >>
>> >> blkkdiscard uses BLKDISCARD ioctl or BLKSECDISCARD ioctl for the secure
>> >> discard.
>> >>
>> >> All data in the discarded region on the device will be lost!
>> >
>> > Hi Karel,
>> >
>> > any progress here ?
>>
>> Where is the patch for blockdev?
>
> There is not.
>
>> I'm still convinced randomly named tools per new kernel ioctl is not
>> what we want. People should get their act together, and not add the
>> tool of the week to util-linux.
>
> And I am still convinced that multiplexing different functionalities
> together into a single tool is not always the best way to go,
> especially when they does not have nothing in common.

They have in common that they operate directly on the raw kernel block device.

This:
  blockdev <verb> [options] <devices>
sounds certainly better than than one tool per every new command.

And it's not only the needlessly duplicated binary, it's primarily
consistency, but also maintenance, documentation, ... which is all
needlessly exploded here.
It's not so much about multiplexing, it's about avoiding needless
duplication for rather exotic functions applying to one and the same
domain, a block device, which already has a command.

util-linux is mandatory in every installation, and it is already one
of the most chaotic and weird collections of random things. We should
certainly be more careful here when coming up with new stuff than
people have been in the past.

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


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux