From: David Rientjes <rientjes@google.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, linux-mm@kvack.org
Subject: Re: [PATCH] mempool: add unlikely and likely hints
Date: Fri, 7 Mar 2014 02:10:58 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1403070210080.31668@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1403061713300.928@file01.intranet.prod.int.rdu2.redhat.com>
On Thu, 6 Mar 2014, Mikulas Patocka wrote:
> This patch adds unlikely and likely hints to the function mempool_free. It
> lays out the code in such a way that the common path is executed
> straighforward and saves a cache line.
>
What observable performance benefit have you seen with this patch and
with what architecture? Could we include some data in the changelog?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-07 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 22:15 Mikulas Patocka
2014-03-07 10:10 ` David Rientjes [this message]
2014-03-07 14:50 ` Mikulas Patocka
2014-03-07 20:54 ` David Rientjes
2014-03-07 21:15 ` Mikulas Patocka
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=alpine.DEB.2.02.1403070210080.31668@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.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