From: Jens Axboe <axboe@fb.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jan Kara <jack@suse.cz>,
Don Zickus <dzickus@redhat.com>, Michal Hocko <mhocko@suse.cz>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [PATCH 00/11] smp: Single IPI cleanups v2
Date: Mon, 24 Feb 2014 14:45:45 -0800 [thread overview]
Message-ID: <530BCB99.6090907@fb.com> (raw)
In-Reply-To: <20140224203743.GF14009@localhost.localdomain>
On 2014-02-24 12:37, Frederic Weisbecker wrote:
> On Mon, Feb 24, 2014 at 09:20:53AM -0800, Jens Axboe wrote:
>> On 2014-02-24 07:39, Frederic Weisbecker wrote:
>>> Hi,
>>>
>>> This version includes:
>>>
>>> * Rename __smp_call_function_single to smp_call_function_single() as
>>> suggested by Christoph.
>>>
>>> * Acks and reviewed-by added.
>>>
>>> * Rebase against -rc4
>>>
>>> Thanks.
>>
>> I'd be happy to take this in, as it's mostly centered around the blk
>> cleanups.
>
> I initially planned to push this tree to Ingo because I have some nohz patches
> that will depend on this set.
>
> But there is indeed quite some block changes there. So I should let these go
> through your tree to avoid bad conflicts. If you never rebase your tree I can
> work on top if it.
Yeah, plus most of the original singe call function (at least the part
where it didn't suck big time) kernel/smp.c functionality in this area
came in through me/block to begin with as well.
I'll queue it up for 3.15.
--
Jens Axboe
prev parent reply other threads:[~2014-02-24 22:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 15:39 [PATCH 00/11] smp: Single IPI cleanups v2 Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 01/11] block: Stop abusing csd.list for fifo_time Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 02/11] block: Remove useless IPI struct initialization Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 03/11] block: Stop abusing rq->csd.list in blk-softirq Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 04/11] smp: Iterate functions through llist_for_each_entry_safe() Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 05/11] smp: Remove unused list_head from csd Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 06/11] smp: Teach __smp_call_function_single() to check for offline cpus Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 07/11] smp: Consolidate the various smp_call_function_single() declensions Frederic Weisbecker
2014-02-24 15:39 ` [PATCH 08/11] smp: Move __smp_call_function_single() below its safe version Frederic Weisbecker
2014-02-24 15:40 ` [PATCH 09/11] watchdog: Simplify a little the IPI call Frederic Weisbecker
2014-02-24 15:40 ` [PATCH 10/11] smp: Remove wait argument from __smp_call_function_single() Frederic Weisbecker
2014-02-24 15:40 ` [PATCH 11/11] smp: Rename __smp_call_function_single() to smp_call_function_single_async() Frederic Weisbecker
2014-02-24 17:20 ` [PATCH 00/11] smp: Single IPI cleanups v2 Jens Axboe
2014-02-24 20:37 ` Frederic Weisbecker
2014-02-24 22:45 ` 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=530BCB99.6090907@fb.com \
--to=axboe@fb.com \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@kernel.org \
--cc=srivatsa.bhat@linux.vnet.ibm.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