From: Manfred Spraul <manfred@colorfullife.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nadia Derbey <Nadia.Derbey@bull.net>,
Pierre Peiffer <peifferp@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [patch 4a/4] ipc: sem optimise simple operations
Date: Mon, 17 Aug 2009 15:02:48 +0200 [thread overview]
Message-ID: <4A8954F8.7040602@colorfullife.com> (raw)
In-Reply-To: <20090817064446.GD9962@wotan.suse.de>
On 08/17/2009 08:44 AM, Nick Piggin wrote:
> OK, well let's just get something in.
>
Good, I would propose the that the following 7 patches should be merged:
http://lkml.org/lkml/2009/8/11/59
http://lkml.org/lkml/2009/8/11/9
http://lkml.org/lkml/2009/8/11/14
http://lkml.org/lkml/2009/8/15/163
http://lkml.org/lkml/2009/8/15/164
http://lkml.org/lkml/2009/8/15/167
http://lkml.org/lkml/2009/8/15/168
Nick: is that ok from your point of view?
> That said, I'm not too unhappy with your version if you feel strongly
> about it.
I would prefer it:
We simply don't know if a wait-for-zero list, only for single sop operations, is a step in the right direction.
Postgres uses single sop operations with just +-1 on one semaphore.
You wrote that your SAP workload also uses +-1.
According to google codesearch, apache, mozilla, mpich all use +-1.
Thus: Who uses single sop, wait for zero?
I'm just afraid that we optimize for the wrong case.
--
Manfred
next prev parent reply other threads:[~2009-08-17 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 19:16 [PATCH] [patch 4a/4] ipc: sem optimise simple operations Manfred Spraul
2009-08-15 4:52 ` Nick Piggin
2009-08-15 10:10 ` Manfred Spraul
2009-08-15 10:38 ` Nick Piggin
[not found] ` <4A86ABF0.2070207@colorfullife.com>
2009-08-15 14:49 ` Nick Piggin
2009-08-15 16:32 ` Manfred Spraul
2009-08-16 4:53 ` Nick Piggin
2009-08-16 5:12 ` Nick Piggin
2009-08-16 10:31 ` Nick Piggin
2009-08-16 11:29 ` Manfred Spraul
2009-08-17 6:44 ` Nick Piggin
2009-08-17 13:02 ` Manfred Spraul [this message]
2009-08-17 13:10 ` Nick Piggin
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=4A8954F8.7040602@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=peifferp@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.