From: Jens Axboe <jaxboe@fusionio.com>
To: Justin TerAvest <teravest@google.com>
Cc: "vgoyal@redhat.com" <vgoyal@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>
Subject: Re: [PATCH] cfq: Remove special treatment for metadata rqs.
Date: Mon, 20 Jun 2011 21:59:52 +0200 [thread overview]
Message-ID: <4DFFA6B8.50506@fusionio.com> (raw)
In-Reply-To: <1308599559-16839-1-git-send-email-teravest@google.com>
On 2011-06-20 21:52, Justin TerAvest wrote:
> There is no consistency among filesystems from what bios (or requests)
> are marked as being metadata. It's interesting to expose this in traces,
> but we shouldn't schedule the requests differently based on whether or
> not they're marked as being metadata.
Agree, we should kill that. What is this patch against? cfq_choose_req()
also has a "choose meta over non-meta" preference.
--
Jens Axboe
next prev parent reply other threads:[~2011-06-20 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 19:52 [PATCH] cfq: Remove special treatment for metadata rqs Justin TerAvest
2011-06-20 19:55 ` Christoph Hellwig
2011-06-20 19:59 ` Jens Axboe [this message]
2011-06-20 20:03 ` Justin TerAvest
2011-06-20 20:05 ` 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=4DFFA6B8.50506@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teravest@google.com \
--cc=vgoyal@redhat.com \
/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.