From: Daniel Borkmann <daniel@iogearbox.net>
To: yalin wang <yalin.wang2010@gmail.com>,
ast@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] bpf: change bpf syacall to use u64 temp variables
Date: Mon, 19 Oct 2015 10:55:22 +0200 [thread overview]
Message-ID: <5624AFFA.2010209@iogearbox.net> (raw)
In-Reply-To: <1445238646-9379-1-git-send-email-yalin.wang2010@gmail.com>
On 10/19/2015 09:10 AM, yalin wang wrote:
> This patch change map_lookup_elem() and map_update_elem() function
> to use u64 temp variable if the key_size or value_size is less than
> u64, we don't need use kmalloc() for these small variables.
>
> Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
From an application PoV that has to make the bpf(2) syscall, how
much do we actually gain from this? I'm curious, did you perform
some benchmarks that show a noticeable difference?
next prev parent reply other threads:[~2015-10-19 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 7:10 [RFC] bpf: change bpf syacall to use u64 temp variables yalin wang
2015-10-19 8:55 ` Daniel Borkmann [this message]
2015-10-19 19:08 ` Alexei Starovoitov
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=5624AFFA.2010209@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yalin.wang2010@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.