BPF Archive on lore.kernel.org
 help / color / Atom feed
From: Joe Stringer <joestringernz@gmail.com>
To: bpf@vger.kernel.org
Cc: lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM/BPF TOPIC] BPF: Various topics
Date: Fri, 14 Feb 2020 16:15:13 -0800
Message-ID: <CAOftzPiUcD3mSdM+GhJ3ma0LRmnifEJVK9RfyH_iX+CcdWY2Sw@mail.gmail.com> (raw)

I'd be interested to participate in the BPF track to discuss the
following topics on BPF, motivated from recent experiences in building
Cilium and a Go eBPF library.

* Improving verifier friendliness. Cilium generates complex BPF
programs which can trigger poor verifier behaviour, eg. a program
would be rejected unless we provided a log buffer of 64MB[0]. Would
like to discuss improvements here like allowing the verifier to treat
the user buffer as a ring buffer via opt-in flag, so that users can
bound the verifier log size and capture only the last N relevant bytes
of verification failure.
* Improving the map iteration interactions. During development of
cilium/ebpf go library, we hit issues defining a clean API providing
guarantees around iteration bounding and completeness of dump[1].
These could be improved via kernel extension, such as opt-in ability
to detect when dumping next key leads to iteration reset to beginning
of map. Also interested in potential for kernel assistance on LRU
eviction handling.
* Development of pure-Go eBPF library. Depending on the audience
appetite this could be hallway track but syncing on library status,
next steps, kernel API pain points.
* Any further updates on socket redirection following LPC discussions.
Detail unclear given that this is in flux.
* Future of BPF interaction with other subsystems / unstable BPF
helpers API per recent discussion on the list.[2]

[0] https://github.com/cilium/cilium/issues/9809 ,
other PRs.
[1] https://github.com/cilium/ebpf/pull/11
[2] https://www.spinics.net/lists/netdev/msg628451.html

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOftzPiUcD3mSdM+GhJ3ma0LRmnifEJVK9RfyH_iX+CcdWY2Sw@mail.gmail.com \
    --to=joestringernz@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

BPF Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/bpf/0 bpf/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 bpf bpf/ https://lore.kernel.org/bpf \
	public-inbox-index bpf

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git