All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: Kay Sievers <kay@vrfy.org>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
	util-linux@vger.kernel.org, kzak@redhat.com
Subject: Re: [PATCH] blkdiscard: add new command
Date: Wed, 26 Sep 2012 16:14:25 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1209261612370.31136@dhcp-187-45.bos.redhat.com> (raw)
In-Reply-To: <CAPXgP11oktXSe3yxdOZCMzNOSrfVawtL95nBuM_NYxB9KPvOdA@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1510 bytes --]

On Wed, 26 Sep 2012, Kay Sievers wrote:

> Date: Wed, 26 Sep 2012 22:04:37 +0200
> From: Kay Sievers <kay@vrfy.org>
> To: Lukáš Czerner <lczerner@redhat.com>
> Cc: util-linux@vger.kernel.org, kzak@redhat.com
> Subject: Re: [PATCH] blkdiscard: add new command
> 
> On Wed, Sep 26, 2012 at 9:47 PM, Lukáš Czerner <lczerner@redhat.com> wrote:
> > On Wed, 12 Sep 2012, Lukas Czerner wrote:
> >
> >> Date: Wed, 12 Sep 2012 17:49:15 -0400
> >> From: Lukas Czerner <lczerner@redhat.com>
> >> To: util-linux@vger.kernel.org, kzak@redhat.com
> >> Cc: Lukas Czerner <lczerner@redhat.com>
> >> 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.

Thanks!
-Lukas

> 
> Thanks,
> Kay
> 

  reply	other threads:[~2012-09-26 20:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 21:49 [PATCH] blkdiscard: add new command Lukas Czerner
2012-09-12 22:43 ` Kay Sievers
2012-09-12 22:47   ` Davidlohr Bueso
2012-09-13 13:37   ` Lukáš Czerner
2012-09-13 13:57     ` Karel Zak
2012-09-13 14:09       ` Lukáš Czerner
2012-09-13 15:33       ` Kay Sievers
2012-09-13 15:52         ` Lukáš Czerner
2012-09-13 15:32     ` Kay Sievers
2012-09-26 19:47 ` Lukáš Czerner
2012-09-26 20:04   ` Kay Sievers
2012-09-26 20:14     ` Lukáš Czerner [this message]
2012-09-26 20:27       ` Kay Sievers
2012-09-26 21:01         ` Lukáš Czerner
2012-09-27  9:42   ` Karel Zak
2012-09-27 15:21     ` Lukáš Czerner
2012-09-27 15:49       ` Martin K. Petersen
2012-09-27 17:03         ` Lukáš Czerner
2012-09-27 17:03           ` Lukáš Czerner
2012-09-27 17:33           ` Martin K. Petersen
2012-09-27 17:33             ` Martin K. Petersen
2012-09-27 23:17         ` Karel Zak
2012-09-27 23:13 ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.1209261612370.31136@dhcp-187-45.bos.redhat.com \
    --to=lczerner@redhat.com \
    --cc=kay@vrfy.org \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.