public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Christoph Hellwig <hch@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Use lockless lists for smp_call_function_single()
Date: Wed, 18 Dec 2013 07:36:44 -0800	[thread overview]
Message-ID: <20131218153644.GA16049@infradead.org> (raw)
In-Reply-To: <1387380302-29552-1-git-send-email-jack@suse.cz>

On Wed, Dec 18, 2013 at 04:24:59PM +0100, 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?

seconded.  Also I think your two cleanups should go before my patch.
I'll also dust up my other patch to use __smp_call_function_single
directly in the block layer once we make progress on these.


  parent reply	other threads:[~2013-12-18 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 15:24 [PATCH 0/3] Use lockless lists for smp_call_function_single() Jan Kara
2013-12-18 15:25 ` [PATCH 1/3] kernel: use lockless list " Jan Kara
2013-12-18 15:25 ` [PATCH 2/3] block: Stop abusing csd.list for fifo_time Jan Kara
2013-12-18 15:25 ` [PATCH 3/3] block: Stop abusing rq->csd.list in blk-softirq Jan Kara
2013-12-18 15:36 ` Christoph Hellwig [this message]
2013-12-18 16:44   ` [PATCH 0/3] Use lockless lists for smp_call_function_single() Jan Kara

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=20131218153644.GA16049@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jaxboe@fusionio.com \
    --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