Netdev List
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Shaohua Li <shli@kernel.org>,
	"netdev @ vger . kernel . org" <netdev@vger.kernel.org>
Cc: Kernel Team <Kernel-team@fb.com>, Shaohua Li <shli@fb.com>,
	Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH] bpf: follow idr code convention
Date: Tue, 27 Mar 2018 22:58:40 +0200	[thread overview]
Message-ID: <9553e6ad-9baf-57bb-2aed-1b2c202b161e@iogearbox.net> (raw)
In-Reply-To: <90243b64dad0d1de21f1a57994d2c43e5facbb33.1522175003.git.shli@fb.com>

On 03/27/2018 08:53 PM, Shaohua Li wrote:
> From: Shaohua Li <shli@fb.com>
> 
> Generally we do a preload before doing idr allocation. This also help
> improve the allocation success rate in memory pressure.
> 
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Shaohua Li <shli@fb.com>

Looks good, applied to bpf-next, thanks Shaohua!

      reply	other threads:[~2018-03-27 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 18:53 [PATCH] bpf: follow idr code convention Shaohua Li
2018-03-27 20:58 ` Daniel Borkmann [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=9553e6ad-9baf-57bb-2aed-1b2c202b161e@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=Kernel-team@fb.com \
    --cc=ast@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shli@fb.com \
    --cc=shli@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