From: Arnd Bergmann <arnd@arndb.de>
To: Yaniv Gardi <ygardi@codeaurora.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 1/2] block: ioctl support for sanitize in eMMC 4.5
Date: Thu, 26 Jul 2012 13:36:31 +0000 [thread overview]
Message-ID: <201207261336.32018.arnd@arndb.de> (raw)
In-Reply-To: <1343208766-8046-2-git-send-email-ygardi@codeaurora.org>
On Wednesday 25 July 2012, Yaniv Gardi wrote:
>
> Adding a new ioctl to support sanitize operation in eMMC
> cards version 4.5.
> The sanitize ioctl support helps performing this operation
> via user application.
>
> Signed-off-by: Yaniv Gardi <ygardi@codeaurora.org>
>
Can you explain how you expect this to be called by a file system?
We've debated this in the past and concluded that we probably
want to do it at the same time as batched discard, but I don't
see if the sanitize request should be sent for each FITRIM
or whether we should better have a separate file system level
ioctl. My feeling is that it would be more useful to call this
feature through a file system level ioctl than through a block
level ioctl, but I guess it makes sense to support both.
Arnd
next prev parent reply other threads:[~2012-07-26 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 9:32 [PATCH v8 0/2] *** adding and exposing SANITIZE capability to the user space via a unique IOCTL *** Yaniv Gardi
2012-07-25 9:32 ` [PATCH v8 1/2] block: ioctl support for sanitize in eMMC 4.5 Yaniv Gardi
2012-07-25 9:32 ` Yaniv Gardi
2012-07-25 10:41 ` merez
2012-07-25 10:41 ` merez
2012-07-26 13:36 ` Arnd Bergmann [this message]
2012-09-09 12:12 ` Yaniv Gardi
2012-09-09 12:12 ` Yaniv Gardi
2012-07-25 9:32 ` [PATCH v8 2/2] mmc: card: Adding " Yaniv Gardi
2012-07-25 9:32 ` Yaniv Gardi
2012-07-25 11:06 ` merez
2012-07-25 11:06 ` merez
2012-07-26 13:27 ` Arnd Bergmann
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=201207261336.32018.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ygardi@codeaurora.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.