mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [RFC PATCH] wfcqueue: implement __wfcq_enqueue_head() (v2)
Date: Sat, 6 Apr 2013 23:51:25 +0000	[thread overview]
Message-ID: <20130406235125.GA12779@dcvr.yhbt.net> (raw)
In-Reply-To: <20130406232908.GA7797@Krystal>

Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> Implement enqueue-to-head. It can run concurrently with enqueue, splice
> to queue, and iteration, but requires a mutex against dequeue and splice
> from queue operations.
> 
> Useful for special-cases where a queue needs to have nodes enqueued into
> its head.
> 
> This patch is only compile-tested.
> 
> Changes since v1:
> * Don't require mutual exclusion between traversals and
>   __wfcq_enqueue_head().
> 
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

Thanks!  The first hunk (sync table comment) conflicted with
my __wfcq_enqueue patch, but other than that I could not benchmark any
regression with my 4-core machine with v4 of my
"epoll: avoid spinlock contention with wfcqueue" patch.

All I needed was "s/__wfcq_prepend/__wfcq_enqueue_head/g" to my original
patch to use the updated API.

I was worried about the cmpxchg at first, but it does not seem to hurt
performance on my 4-core system.  In fact, it was slightly better
(but within margin of error)

time ./eponeshotmt -c 1000000 -w 4 -t 4 -f 10
real    0m 5.78s
user    0m 1.20s
sys     0m 21.90s

Tested-by: Eric Wong <normalperson@yhbt.net>

Hopefully somebody can test my epoll patches with more cores/threads :)

  reply	other threads:[~2013-04-06 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 23:29 Mathieu Desnoyers
2013-04-06 23:51 ` Eric Wong [this message]
2013-04-07 15:02   ` Mathieu Desnoyers

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=20130406235125.GA12779@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@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

all inboxes | Powered by JetHome®