public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Shaohua Li <shli@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	jh80.chung@samsung.com, linux-mmc@vger.kernel.org
Subject: Re: [RFC PATCH] request: teach the device more intelligent
Date: Thu, 11 Aug 2011 10:20:49 -0400	[thread overview]
Message-ID: <20110811142049.GE8552@redhat.com> (raw)
In-Reply-To: <CAH9JG2XTOOS5GGO7howP+SLbTkj0xUJHPisFYPZfkJddWeKQ4Q@mail.gmail.com>

On Thu, Aug 11, 2011 at 09:36:04AM +0900, Kyungmin Park wrote:

[...]
> No, no need to consistent. the context id id only valid when several
> requests are request the I/O simultaneously
> e.g.,
> App1 requests A, B, C, D, ...
> App2 requests a, b, c, d, ...
> App2 requests 1, 2, 3, 4, 5, ...
> with following order, A, B, a, 1, C, b, 2, ...
> 
> The current eMMC can't handle these operation.
> 
> Instead using context, it can teach the these operation comes from
> using context ID. and finally can place the request in-order at card
> internally.
> 
> Open Context ID operation, perform I/O with context Id, ...., and
> Close Context ID operation until queue is empty.

Hi Kyungmin,

So once we have context information, we want to process all the requests
from the same context together? IOW, we expect that driver will have
multiple requests in flight from various context and it will batch the
requests from same context together?

How does that help? Is it something related to seeking? If yes, then just
setting the rotational=1 should help as CFQ will sequence all the
sequential IO where it can. For random IO, anyway optimization will not
help. May be it is about something else which I am completely missing.
Some details here will help.

Thanks
Vivek

  parent reply	other threads:[~2011-08-11 14:21 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
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 [this message]
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=20110811142049.GE8552@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=jh80.chung@samsung.com \
    --cc=kmpark@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shli@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