All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: 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 12:08:36 -0700	[thread overview]
Message-ID: <20151019190835.GA19852@Alexeis-MBP.westell.com> (raw)
In-Reply-To: <1445238646-9379-1-git-send-email-yalin.wang2010@gmail.com>

On Mon, Oct 19, 2015 at 03:10:46PM +0800, 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>
> ---
>  kernel/bpf/syscall.c | 30 ++++++++++++++++++++----------
>  1 file changed, 20 insertions(+), 10 deletions(-)
> 
> diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
> index f640e5f..c82d7bf 100644
> --- a/kernel/bpf/syscall.c
> +++ b/kernel/bpf/syscall.c
> @@ -189,7 +189,8 @@ static int map_lookup_elem(union bpf_attr *attr)
>  	void __user *uvalue = u64_to_ptr(attr->value);
>  	int ufd = attr->map_fd;
>  	struct bpf_map *map;
> -	void *key, *value, *ptr;
> +	u64 key_buf, value_buf;
> +	void *key = &key_buf, *value = &value_buf, *ptr;
>  	struct fd f;
>  	int err;
>  
> @@ -202,7 +203,8 @@ static int map_lookup_elem(union bpf_attr *attr)
>  		return PTR_ERR(map);
>  
>  	err = -ENOMEM;
> -	key = kmalloc(map->key_size, GFP_USER);
> +	if (map->key_size > sizeof(u64))
> +		key = kmalloc(map->key_size, GFP_USER);

I think it's a good optimization for common case.
Performance numbers would be good to prove the point.
Thanks


      parent reply	other threads:[~2015-10-19 19:08 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
2015-10-19 19:08 ` Alexei Starovoitov [this message]

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=20151019190835.GA19852@Alexeis-MBP.westell.com \
    --to=alexei.starovoitov@gmail.com \
    --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.