From: Jens Axboe <axboe@fb.com>
To: Michael Callahan <coder.callahan@gmail.com>,
Jens Axboe <axboe@kernel.dk>
Cc: Michael Callahan <michaelcallahan@fb.com>, <linux-block@vger.kernel.org>
Subject: Re: [PATCH 1/1] block: Use per-cpu partition in_flight counters.
Date: Mon, 16 May 2016 15:17:44 -0600 [thread overview]
Message-ID: <573A38F8.7070804@fb.com> (raw)
In-Reply-To: <CADm5WxMq=2yhvg44=-kDCWs09+t6UqE2TgQdpaSVYs5qyfVvyA@mail.gmail.com>
On 05/16/2016 02:06 PM, Michael Callahan wrote:
> I don't feel strongly about pursuing this one. I could not measure a
> difference either way.
That answers that, then :-)
> This mailing list appears to be for patch submissions. Where are the
> requests for review and discussion of half baked ideas happening?
The list serves both purposes. If you're just tossing something out
there, prefixing the submission with RFC (request for comment) could
help. Otherwise people assume it's a full patch submission, something
that you are ready to land in mainline.
--
Jens Axboe
prev parent reply other threads:[~2016-05-16 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 22:09 [PATCH 1/1] block: Use per-cpu partition in_flight counters Michael Callahan
2016-05-10 22:18 ` Jens Axboe
2016-05-16 20:06 ` Michael Callahan
2016-05-16 21:17 ` Jens Axboe [this message]
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=573A38F8.7070804@fb.com \
--to=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=coder.callahan@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=michaelcallahan@fb.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.