From: Andi Kleen <ak@linux.intel.com>
To: Kent Overstreet <koverstreet@google.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Zach Brown <zab@zabbo.net>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH][WIP] dio rewrite
Date: Mon, 11 Feb 2013 17:24:13 -0800 [thread overview]
Message-ID: <20130212012413.GA30387@tassilo.jf.intel.com> (raw)
In-Reply-To: <20130212005326.GA6592@moria.home.lan>
On Mon, Feb 11, 2013 at 04:53:26PM -0800, Kent Overstreet wrote:
> I finally started hacking on the dio code, and it's far from done but
> it's turning out better than I expected so I thought I'd show off what
> I've got so far.
The critical metric for some of the highend workloads
is the number of cache lines touched in the submission path
(especially potentially modified ones). How does your new code fare on that?
-Andi
next prev parent reply other threads:[~2013-02-12 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 0:53 [PATCH][WIP] dio rewrite Kent Overstreet
2013-02-12 1:24 ` Andi Kleen [this message]
2013-02-12 1:33 ` Kent Overstreet
-- strict thread matches above, loose matches on Subject: below --
2013-02-14 2:10 Kent Overstreet
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=20130212012413.GA30387@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=koverstreet@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zab@zabbo.net \
/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;
as well as URLs for NNTP newsgroup(s).