From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Andrew Morton <akpm@linux-foundation.org>,
George Spelvin <linux@horizon.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] ipc/msg: Implement lockless pipelined wakeups
Date: Tue, 3 Nov 2015 15:51:39 +0100 [thread overview]
Message-ID: <5638C9FB.9080404@linutronix.de> (raw)
In-Reply-To: <563595C3.5090609@colorfullife.com>
On 11/01/2015 05:32 AM, Manfred Spraul wrote:
> Hi Sebastian,
Hi Manfred,
> with regards to functional tests:
> fakeroot is a heavy system V user (at least if it is configured for sysv).
> "make -j" under fakeroot was a useful stresstest
I don't see the msgsnd/msgrcv syscalls here. I do see others, sem
related for instance….
> with regards to benchmarks:
> I've attached one of my files.
Thank you. On 'AMD A10-7800 Radeon R7, 12 Compute Cores 4C+8G' I have
here:
test | before | after | diff
-----------------|------------|-------------
pmsg-shared 8 60 | 52,386,363 | 56,455,763 | + ~7.77%
pmsg-shared 2 60 | 69,200,531 | 73,346,420 | + ~5.99%
so it improved a little :)
> Otherwise: Nice!
>
> --
> Manfred
>
Sebastian
prev parent reply other threads:[~2015-11-03 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:26 [PATCH] ipc/msg: Implement lockless pipelined wakeups Sebastian Andrzej Siewior
2015-10-30 22:30 ` George Spelvin
2015-11-03 14:01 ` Sebastian Andrzej Siewior
2015-10-31 10:31 ` Thomas Gleixner
2015-10-31 13:02 ` George Spelvin
2015-10-31 15:17 ` Thomas Gleixner
2015-10-31 18:54 ` Davidlohr Bueso
2015-10-31 19:06 ` Davidlohr Bueso
2015-11-03 14:15 ` Sebastian Andrzej Siewior
2015-11-03 14:11 ` Sebastian Andrzej Siewior
2015-11-01 4:32 ` Manfred Spraul
2015-11-03 14:51 ` Sebastian Andrzej Siewior [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=5638C9FB.9080404@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=manfred@colorfullife.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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