linux-kernel - Re: [RFC PATCH v2] support ioctl for tunable user request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Aug 2011 23:17:25 +0800
From:	Lin Ming <lxy@...pku.edu.cn>
To:	Kyungmin Park <kmpark@...radead.org>
Cc:	Jaehoon Chung <jh80.chung@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jens Axboe <jaxboe@...ionio.com>,
	Arnd Bergmann <arnd.bergmann@...aro.org>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [RFC PATCH v2] support ioctl for tunable user request

On Mon, Aug 29, 2011 at 10:01 PM, Kyungmin Park <kmpark@...radead.org> wrote:
> On Mon, Aug 29, 2011 at 7:11 PM, Jaehoon Chung <jh80.chung@...sung.com> wrote:
>> Hi
>>
>> Lin Ming wrote:
>>> On Mon, Aug 29, 2011 at 4:15 PM, Jaehoon Chung <jh80.chung@...sung.com> wrote:
>>>> This patch is added the ioctl for tunable user request.
>>>
>>> Hi,
>>>
>>> What's the use case for this new ioctl?
>
> The below is the just mmc example.
>
> The main reason is that there's no way to know system or I/O idle, so
> user provides the hint. Using user based I/O, device can TUNE the
> device itself. In case of MMC, background operation can be used.
>
> and another difference from other user request, it's just trigger the
> device tune request, no need to wait the request is done.

OK.

After read the previous patch at:
http://marc.info/?l=linux-mmc&m=131407402925988&w=2

I now get better understanding what "tunable user request" mean.

Thanks.

>
> Thank you,
> Kyungmin Park
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/