bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Rostecki <mrostecki@opensuse.org>
To: mrostecki@opensuse.org
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
	Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpftool/libbpf: Add probe for large INSN limit
Date: Fri, 27 Dec 2019 18:14:48 +0000	[thread overview]
Message-ID: <20191227181448.GA452@wotan.suse.de> (raw)
In-Reply-To: <20191227105346.867-1-mrostecki@opensuse.org>

On Fri, Dec 27, 2019 at 11:53:44AM +0100, mrostecki@opensuse.org wrote:
> From: Michal Rostecki <mrostecki@opensuse.org>
> 
> This series implements a new BPF feature probe which checks for the
> commit c04c0d2b968a ("bpf: increase complexity limit and maximum program
> size"), which increases the maximum program size to 1M. It's based on
> the similar check in Cilium, althogh Cilium is already aiming to use
> bpftool checks and eventually drop all its custom checks.
> 
> Examples of outputs:
> 
> # bpftool feature probe
> [...]
> Scanning miscellaneous eBPF features...
> Large complexity limit and maximum program size (1M) is available
> 
> # bpftool feature probe macros
> [...]
> /*** eBPF misc features ***/
> #define HAVE_HAVE_LARGE_INSN_LIMIT
> 
> # bpftool feature probe -j | jq '.["misc"]'
> {
>   "have_large_insn_limit": true
> }
> 
> Michal Rostecki (2):
>   libbpf: Add probe for large INSN limit
>   bpftool: Add misc secion and probe for large INSN limit
> 
>  tools/bpf/bpftool/feature.c   | 18 ++++++++++++++++++
>  tools/lib/bpf/libbpf.h        |  1 +
>  tools/lib/bpf/libbpf.map      |  1 +
>  tools/lib/bpf/libbpf_probes.c | 23 +++++++++++++++++++++++
>  4 files changed, 43 insertions(+)
> 
> -- 
> 2.16.4
> 

Sorry for sending this twice! I didn't see the thread immediately after
sending the first time, so I though there is some problem with my
@opensuse.org alias or SMTP server not accepting it. Please review this
series, since I'm using @opensuse.org alias for upstream development
more frequently than @suse.de.

  parent reply	other threads:[~2019-12-27 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 10:53 [PATCH bpf-next 0/2] bpftool/libbpf: Add probe for large INSN limit mrostecki
2019-12-27 10:53 ` [PATCH bpf-next 1/2] libbpf: " mrostecki
2019-12-27 10:53 ` [PATCH bpf-next 2/2] bpftool: Add misc secion and " mrostecki
2019-12-27 18:14 ` Michal Rostecki [this message]
2019-12-27 11:06 [PATCH bpf-next 0/2] bpftool/libbpf: Add " Michal Rostecki

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=20191227181448.GA452@wotan.suse.de \
    --to=mrostecki@opensuse.org \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).