From: Namhyung Kim <namhyung@gmail.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>,
jaxboe@fusionio.com, linux-kernel@vger.kernel.org, arnd@arndb.de,
jh80.chung@samsung.com
Subject: Re: [RFC PATCH] request: teach the device more intelligent
Date: Wed, 10 Aug 2011 11:16:15 +0900 [thread overview]
Message-ID: <87ipq6xb80.fsf@gmail.com> (raw)
In-Reply-To: <CAH9JG2UqMD=S3e+BupO+8dfEZQy5eZWO2gMhbTPmmjHJFOimtw@mail.gmail.com> (Kyungmin Park's message of "Tue, 9 Aug 2011 23:04:41 +0900")
Kyungmin Park <kmpark@infradead.org> writes:
> Cc the correct email address of jens
>
> On Tue, Aug 9, 2011 at 12:47 PM, Kyungmin Park <kmpark@infradead.org> wrote:
>> Hi Jens
>>
>> Now eMMC device requires the upper layer information to improve the data
>> performance and reliability.
>>
>> . Context ID
>> Using the context information, it can sort out the data internally and improve the performance.
>> The main problem is that it's needed to define "What's the context".
>> Actually I expect cfq queue has own unique ID but it doesn't so decide to use the pid instead
>>
>> . Data Tag
>> Using the Data Tag (1-bit information), It writes the data at SLC area when it's hot data. So it can make the chip more reliable.
>> First I expect the REQ_META but current ext4 doesn't pass the WRITE_META. only use the READ_META. so it needs to investigate it.
>>
>> With these characteristics, it's helpful to teach the device. After some consideration. it's needed to pass out these information at request data structure.
>>
>> Can you give your opinions and does it proper fields at requests?
>>
>> Thank you,
>> Kyungmin Park
>> ---
>> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
>> index 1f96ad6..d73bfa7 100644
>> --- a/block/cfq-iosched.c
>> +++ b/block/cfq-iosched.c
>> @@ -3790,6 +3790,7 @@ new_queue:
>> rq->elevator_private[0] = cic;
>> rq->elevator_private[1] = cfqq;
>> rq->elevator_private[2] = cfq_ref_get_cfqg(cfqq->cfqg);
>> + rq->hint.context = (int) cfqq->pid;
>> spin_unlock_irqrestore(q->queue_lock, flags);
>> return 0;
>>
>> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
>> index 0e67c45..0145c10 100644
>> --- a/include/linux/blkdev.h
>> +++ b/include/linux/blkdev.h
>> @@ -69,6 +69,14 @@ enum rq_cmd_type_bits {
>> REQ_TYPE_ATA_PC,
>> };
>>
>> +/*
>> + * request hint
>> + */
>> +struct request_hint {
>> + int context; /* Context ID */
>> + int hot:1; /* Hot/cold data */
This 1-bit member should be a type of unsigned?
Thanks.
next prev parent reply other threads:[~2011-08-10 2:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 3:47 [RFC PATCH] request: teach the device more intelligent Kyungmin Park
2011-08-09 14:04 ` Kyungmin Park
2011-08-10 2:16 ` Namhyung Kim [this message]
2011-08-09 18:52 ` Jens Axboe
2011-08-09 23:43 ` Kyungmin Park
2011-08-10 8:08 ` Jens Axboe
2011-08-10 8:42 ` Kyungmin Park
2011-08-10 8:47 ` Shaohua Li
2011-08-10 8:55 ` Kyungmin Park
2011-08-10 9:06 ` Jens Axboe
2011-08-11 0:29 ` Shaohua Li
2011-08-11 0:36 ` Kyungmin Park
2011-08-11 0:40 ` Kyungmin Park
2011-08-11 1:01 ` Shaohua Li
2011-08-11 14:20 ` Vivek Goyal
2011-08-12 2:20 ` Kyungmin Park
2011-08-11 7:56 ` Jens Axboe
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=87ipq6xb80.fsf@gmail.com \
--to=namhyung@gmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=jaxboe@fusionio.com \
--cc=jh80.chung@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox