From: "Björn Töpel" <bjorn.topel@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: "Daniel Borkmann" <daniel@iogearbox.net>,
Netdev <netdev@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Björn Töpel" <bjorn.topel@intel.com>, bpf <bpf@vger.kernel.org>,
"Magnus Karlsson" <magnus.karlsson@gmail.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>
Subject: Re: [RFC PATCH bpf-next 2/4] bpf: introduce BPF dispatcher
Date: Thu, 14 Nov 2019 16:03:57 +0100 [thread overview]
Message-ID: <CAJ+HfNhRKFGOsv5Nbq5T9NHk=ZcHnK40_jR8bpqNC1GYk8ovTA@mail.gmail.com> (raw)
In-Reply-To: <874kz6o6bs.fsf@toke.dk>
On Thu, 14 Nov 2019 at 15:55, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
[...]
> I don't really have anything to back it up, but my hunch is that only 4
> entries will end up being a limit that people are going to end up
> hitting. And since the performance falls off quite the cliff after
> hitting that limit, I do fear that this is something we will hear about
> quite emphatically :)
>
Hmm, maybe. I have 8 i40e netdevs on my test machine, all running XDP,
but I don't think that's normal for deployments. ;-)
Björn
next prev parent reply other threads:[~2019-11-14 15:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 20:47 [RFC PATCH bpf-next 0/4] Introduce xdp_call.h and the BPF dispatcher Björn Töpel
2019-11-13 20:47 ` [RFC PATCH bpf-next 1/4] bpf: teach bpf_arch_text_poke() jumps Björn Töpel
2019-11-13 20:47 ` [RFC PATCH bpf-next 2/4] bpf: introduce BPF dispatcher Björn Töpel
2019-11-13 21:40 ` Edward Cree
2019-11-14 6:29 ` Björn Töpel
2019-11-14 10:18 ` Edward Cree
2019-11-14 11:21 ` Björn Töpel
2019-11-14 13:58 ` Peter Zijlstra
2019-11-14 12:31 ` Toke Høiland-Jørgensen
2019-11-14 13:03 ` Daniel Borkmann
2019-11-14 13:09 ` Toke Høiland-Jørgensen
2019-11-14 13:56 ` Björn Töpel
2019-11-14 14:55 ` Toke Høiland-Jørgensen
2019-11-14 15:03 ` Björn Töpel [this message]
2019-11-14 15:12 ` Toke Høiland-Jørgensen
2019-11-15 0:30 ` Alexei Starovoitov
2019-11-15 7:56 ` Björn Töpel
2019-11-15 21:58 ` Alexei Starovoitov
2019-11-18 10:03 ` Björn Töpel
2019-11-18 19:36 ` Andrii Nakryiko
2019-11-18 20:11 ` Björn Töpel
2019-11-13 20:47 ` [RFC PATCH bpf-next 3/4] xdp: introduce xdp_call Björn Töpel
2019-11-13 20:47 ` [RFC PATCH bpf-next 4/4] i40e: start using xdp_call.h Björn Töpel
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='CAJ+HfNhRKFGOsv5Nbq5T9NHk=ZcHnK40_jR8bpqNC1GYk8ovTA@mail.gmail.com' \
--to=bjorn.topel@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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).