From: Ingo Molnar <mingo@elte.hu>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] signals: don't copy siginfo_t on dequeue
Date: Thu, 26 Feb 2009 21:27:11 +0100 [thread overview]
Message-ID: <20090226202711.GB23446@elte.hu> (raw)
In-Reply-To: <20090226201905.GA8548@redhat.com>
* Oleg Nesterov <oleg@redhat.com> wrote:
> On 02/26, Vegard Nossum wrote:
> >
> > 2009/2/26 Ingo Molnar <mingo@elte.hu>:
> > >
> > > I.e. shouldnt we have seen a speedup, due to not having to copy
> > > the siginfo structure?
>
> I am puzzled by these numbers too. I can't understand how this
> patch can make any difference.
Measurement noise perhaps. Especially such microbenchmarks can
be very sensitive to cache layout, etc.
Ingo
next prev parent reply other threads:[~2009-02-26 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 18:44 Vegard Nossum
2009-02-26 18:50 ` Ingo Molnar
2009-02-26 19:10 ` Vegard Nossum
2009-02-26 20:19 ` Oleg Nesterov
2009-02-26 20:27 ` Ingo Molnar [this message]
2009-02-26 19:15 ` Oleg Nesterov
2009-02-26 20:18 ` Vegard Nossum
2009-02-26 20:36 ` Oleg Nesterov
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=20090226202711.GB23446@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@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 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®