From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH] bpf: cpumap micro-optimization in cpu_map_enqueue
Date: Wed, 1 Nov 2017 09:12:11 -0700 [thread overview]
Message-ID: <20171101161210.55ekkcrkrsgltvx6@ast-mbp> (raw)
In-Reply-To: <150953668583.30172.5069550217700139382.stgit@firesoul>
On Wed, Nov 01, 2017 at 12:44:45PM +0100, Jesper Dangaard Brouer wrote:
> Discovered that the compiler laid-out asm code in suboptimal way
> when studying perf report during benchmarking of cpumap. Help
> the compiler by the marking unlikely code paths.
>
> Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2017-11-01 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 11:44 [net-next PATCH] bpf: cpumap micro-optimization in cpu_map_enqueue Jesper Dangaard Brouer
2017-11-01 13:54 ` John Fastabend
2017-11-01 14:18 ` Jesper Dangaard Brouer
2017-11-01 16:12 ` Alexei Starovoitov [this message]
2017-11-02 7:14 ` David Miller
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=20171101161210.55ekkcrkrsgltvx6@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=brouer@redhat.com \
--cc=netdev@vger.kernel.org \
/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