From: Jens Axboe <axboe@kernel.dk>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Alexander Gordeev <agordeev@redhat.com>,
Kent Overstreet <kmo@daterainc.com>,
Oleg Nesterov <oleg@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] percpu_ida: Various tweaks
Date: Mon, 11 Nov 2013 14:25:18 -0700 [thread overview]
Message-ID: <1F29C616-F4BD-4BB8-9128-4B19AF490E9E@kernel.dk> (raw)
In-Reply-To: <1384204833.12281.9.camel@haakon3.risingtidesystems.com>
On 11/11/2013, at 14.20, "Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:
>
>> On Mon, 2013-11-11 at 12:39 -0700, Jens Axboe wrote:
>>> On Mon, Nov 11 2013, Alexander Gordeev wrote:
>>>> On Mon, Oct 28, 2013 at 02:29:06PM -0700, Nicholas A. Bellinger wrote:
>>>> I'll wait for Kent's feedback on these, and end-up dropping the
>>>> blk-mq-tag part from Patch #5 for the moment..
>>>
>>> Hi Nicholas,
>>>
>>> I am bit uncertain regarding the process concerning your and Jens trees.
>>> Are you planning to pull Shaohua's percpu_ida conversion?
>>
>> The submitted blk-mq bits have the conversion, the old tagging is no
>> longer active/maintained. So any work on this going forward will have to
>> be based on the percpu ida conversion.
>
> What Jen's said..
I'm going to start calling you Nick, if you keep misspelling my name.
Jens
next prev parent reply other threads:[~2013-11-11 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 10:04 Alexander Gordeev
2013-10-28 21:23 ` Kent Overstreet
2013-10-28 21:29 ` Alexander Gordeev
2013-10-28 21:29 ` Nicholas A. Bellinger
2013-10-29 7:56 ` Alexander Gordeev
2013-11-11 19:34 ` Alexander Gordeev
2013-11-11 19:39 ` Jens Axboe
2013-11-11 21:20 ` Nicholas A. Bellinger
2013-11-11 21:25 ` Jens Axboe [this message]
2014-01-14 11:41 ` Alexander Gordeev
2014-01-15 23:04 ` 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=1F29C616-F4BD-4BB8-9128-4B19AF490E9E@kernel.dk \
--to=axboe@kernel.dk \
--cc=agordeev@redhat.com \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=oleg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®