From: Jaehoon Chung <jh80.chung@samsung.com>
To: Lin Ming <lxy@ss.pku.edu.cn>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <jaxboe@fusionio.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RFC PATCH v2] support ioctl for tunable user request
Date: Mon, 29 Aug 2011 19:11:18 +0900 [thread overview]
Message-ID: <4E5B65C6.6070300@samsung.com> (raw)
In-Reply-To: <CAF1ivSaveqVs8dGF+HZBytJpUpTJPysUox=qmHDTFQvqBmm+rw@mail.gmail.com>
Hi
Lin Ming wrote:
> On Mon, Aug 29, 2011 at 4:15 PM, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>> This patch is added the ioctl for tunable user request.
>
> Hi,
>
> What's the use case for this new ioctl?
>
In my case, this ioctl is used the background operation for eMMC.
In eMMC's case, background operation(BKOPS) is supported.
(but that is running with only card notifier, so i added new ioctl for user request)
if we send the BKOPS request, card is notified to need the BKOPS.
then running background operation. (Then user's responsibility is done)
In future, i think that other block device should be used this ioctl.
(if supported like BKOPS)
Regard,
Jaehoon Chung
next prev parent reply other threads:[~2011-08-29 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 8:15 [RFC PATCH v2] support ioctl for tunable user request Jaehoon Chung
2011-08-29 8:49 ` Lin Ming
2011-08-29 10:11 ` Jaehoon Chung [this message]
2011-08-29 14:01 ` Kyungmin Park
2011-08-29 15:17 ` Lin Ming
2011-09-05 8:49 ` Kyungmin Park
2011-09-05 9:15 ` Christoph Hellwig
2011-09-05 11:47 ` Kyungmin Park
2011-09-05 12:18 ` Christoph Hellwig
2011-09-05 12:40 ` Kyungmin Park
2011-09-05 15:04 ` Arnd Bergmann
2011-09-06 4:24 ` Kyungmin Park
2011-09-08 15:47 ` Arnd Bergmann
2011-09-08 15:54 ` Christoph Hellwig
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=4E5B65C6.6070300@samsung.com \
--to=jh80.chung@samsung.com \
--cc=arnd.bergmann@linaro.org \
--cc=jaxboe@fusionio.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lxy@ss.pku.edu.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox