From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3 v2] Use lockless lists for smp_call_function_single()
Date: Thu, 19 Dec 2013 08:31:54 -0700 [thread overview]
Message-ID: <20131219153154.GI30200@kernel.dk> (raw)
In-Reply-To: <1387387418-10005-1-git-send-email-jack@suse.cz>
On Wed, Dec 18 2013, Jan Kara wrote:
> Hello,
>
> these three patches make smp_call_function_single() use lockless lists and
> cleanup abuse of csd.list in the block layer. I have some use for lockless
> smp_call_function_single() in printk code and that's why I've picked up
> Christoph's patch. Jens, can you have a look at the series please?
>
> Changes since v1:
> * Reordered patches to a more sensible order.
Thanks Jan, I'll throw this into the testing mix for 3.14. Will be a
little delayed over christmas, with holidays and family visiting.
--
Jens Axboe
next prev parent reply other threads:[~2013-12-19 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 17:23 [PATCH 0/3 v2] Use lockless lists for smp_call_function_single() Jan Kara
2013-12-18 17:23 ` [PATCH 1/3] block: Stop abusing csd.list for fifo_time Jan Kara
2013-12-18 20:50 ` Jan Kara
2013-12-18 17:23 ` [PATCH 1/3] kernel: use lockless list for smp_call_function_single() Jan Kara
2013-12-18 17:23 ` [PATCH 2/3] block: Stop abusing csd.list for fifo_time Jan Kara
2013-12-18 17:23 ` [PATCH 2/3] block: Stop abusing rq->csd.list in blk-softirq Jan Kara
2013-12-18 20:50 ` Jan Kara
2013-12-18 17:23 ` [PATCH 3/3] " Jan Kara
2013-12-18 17:23 ` [PATCH 3/3] kernel: use lockless list for smp_call_function_single() Jan Kara
2013-12-18 20:51 ` Jan Kara
2013-12-18 20:50 ` [PATCH 0/3 v2] Use lockless lists " Jan Kara
2013-12-19 15:31 ` Jens Axboe [this message]
2014-01-07 15:47 ` Christoph Hellwig
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=20131219153154.GI30200@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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