From: Kyungmin Park <kmpark@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <jaxboe@fusionio.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Lin Ming <lxy@ss.pku.edu.cn>
Subject: Re: [RFC PATCH v2] support ioctl for tunable user request
Date: Mon, 5 Sep 2011 20:47:58 +0900 [thread overview]
Message-ID: <CAH9JG2UevPYDOFycLGbh+zu9CyoDx8N8qnCzMy0Lq2b+06EatA@mail.gmail.com> (raw)
In-Reply-To: <20110905091540.GA22014@infradead.org>
Hi Christoph,
On Mon, Sep 5, 2011 at 6:15 PM, Christoph Hellwig <hch@infradead.org> wrote:
> So what the heck is a tunable request supposed to be? How does it
> qualify for beeing a generic request/bio type?
The concept is similar with DISCARD request except no-wait for request complete
#define REQ_DISCARD (1 << __REQ_DISCARD)
+#define REQ_TUNE (1 << __REQ_TUNE)
As it's hard to detect the idle time at device level, user send the
tune request to device when idle.
Thank you,
Kyungmin Park
next prev parent reply other threads:[~2011-09-05 11:52 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
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 [this message]
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=CAH9JG2UevPYDOFycLGbh+zu9CyoDx8N8qnCzMy0Lq2b+06EatA@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=jh80.chung@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 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.