From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Ryan Goodfellow <rgoodfel@isi.edu>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Subject: Re: zero-copy between interfaces
Date: Tue, 14 Jan 2020 08:47:54 +0100 [thread overview]
Message-ID: <CAJ8uoz2o0gQJOFjSsw3NEJ4vdyKfoLgj=vF3ZTj0v3bbA993qw@mail.gmail.com> (raw)
In-Reply-To: <877e1vwaep.fsf@toke.dk>
On Mon, Jan 13, 2020 at 6:09 PM Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> Ryan Goodfellow <rgoodfel@isi.edu> writes:
>
> > On Mon, Jan 13, 2020 at 11:43:02AM +0100, Toke Høiland-Jørgensen wrote:
> >>> Magnus Karlsson <magnus.karlsson@gmail.com> writes:
> >>>> On Mon, Jan 13, 2020 at 1:28 AM Ryan Goodfellow <rgoodfel@isi.edu> wrote:
> >>>> The reason for wanting large memory maps is that our use case for XDP is network
> >>>> emulation - and sometimes that means introducing delay factors that can require
> >>>> a rather large in-memory packet buffers.
> >>>>
> >>>> If there is interest in including this program in the official BPF samples I'm happy to
> >>>> submit a patch. Any comments on the program are also much appreciated.
> >>>
> >>> More examples are always useful, but the question is if it should
> >>> reside in samples or outside the kernel in some other repo? Is there
> >>> some good place in xdp-project github that could be used for this
> >>> purpose?
> >>
> >> We could certainly create something; either a new xdp-samples
> >> repository, or an example-programs/ subdir of the xdp-tutorial? Which of
> >> those makes the most sense depends on the size of the program I think...
> >>
> >> -Toke
> >>
> >
> > I'm happy to provide patches or pull-requests in either case. The userspace
> > program is 1 file with 555 lines and the BPF program is 28 lines. I've
> > tested the userspace program with the 5.5 kernel. The BPF program requires
> > clang-9 to work properly (due to BTF features IIRC).
> >
> > - https://gitlab.com/mergetb/tech/network-emulation/kernel/blob/v5.5-moa/samples/bpf/xdpsock_multidev.c
> > - https://gitlab.com/mergetb/tech/network-emulation/kernel/blob/v5.5-moa/samples/bpf/xdpsock_multidev_kern.c
> >
> > The primary usefulness of this program relative to what's out there is
> > that it pushes packets between interfaces using a common memory map.
>
> Hmm, yeah, this could live in either samples or as standalone. IDK,
> Magnus what do you think?
Let us try the kernel samples first. Then and if the folks on the
mailing list do not want more samples in there, we fall back on the
xdp-tutorial repo.
/Magnus
> -Toke
>
next prev parent reply other threads:[~2020-01-14 7:48 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 0:18 zero-copy between interfaces Ryan Goodfellow
2020-01-13 9:16 ` Magnus Karlsson
2020-01-13 10:43 ` Toke Høiland-Jørgensen
2020-01-13 15:25 ` Ryan Goodfellow
2020-01-13 17:09 ` Toke Høiland-Jørgensen
2020-01-14 7:47 ` Magnus Karlsson [this message]
2020-01-14 8:11 ` Toke Høiland-Jørgensen
2020-01-13 15:11 ` Ryan Goodfellow
2020-01-14 9:59 ` Magnus Karlsson
2020-01-14 20:52 ` Ryan Goodfellow
2020-01-15 1:41 ` Ryan Goodfellow
2020-01-15 7:40 ` Magnus Karlsson
2020-01-15 8:20 ` Magnus Karlsson
2020-01-16 2:04 ` Ryan Goodfellow
2020-01-16 14:32 ` Magnus Karlsson
2020-01-17 9:45 ` Magnus Karlsson
2020-01-17 17:05 ` Ryan Goodfellow
2020-01-21 7:34 ` Magnus Karlsson
2020-01-21 13:40 ` Maxim Mikityanskiy
2020-01-22 21:43 ` Ryan Goodfellow
2020-01-27 14:01 ` Maxim Mikityanskiy
2020-01-27 15:54 ` Magnus Karlsson
2020-01-30 9:37 ` Maxim Mikityanskiy
2020-01-30 9:59 ` Magnus Karlsson
2020-01-30 11:40 ` Magnus Karlsson
2020-02-04 16:10 ` Magnus Karlsson
2020-02-05 13:31 ` Magnus Karlsson
2020-02-06 14:56 ` Maxim Mikityanskiy
2020-02-07 9:01 ` Magnus Karlsson
2020-01-17 17:40 ` William Tu
2020-01-13 11:41 ` Jesper Dangaard Brouer
2020-01-13 15:28 ` Ryan Goodfellow
2020-01-13 17:04 ` Jesper Dangaard Brouer
2020-01-17 17:54 ` Ryan Goodfellow
2020-01-18 10:14 ` Jesper Dangaard Brouer
2020-01-18 14:08 ` Ryan Goodfellow
2020-01-26 4:53 ` Dan Siemon
2020-01-17 12:32 ` Björn Töpel
2020-01-17 12:32 ` [Intel-wired-lan] " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-01-17 17:16 ` Ryan Goodfellow
2020-01-17 17:16 ` [Intel-wired-lan] " Ryan Goodfellow
2020-01-17 18:10 ` Ryan Goodfellow
2020-01-17 18:10 ` [Intel-wired-lan] " Ryan Goodfellow
2020-01-20 8:24 ` Magnus Karlsson
2020-01-20 8:24 ` [Intel-wired-lan] " Magnus Karlsson
2020-01-20 18:33 ` Ryan Goodfellow
2020-01-20 18:33 ` [Intel-wired-lan] " Ryan Goodfellow
2020-01-20 17:04 ` Björn Töpel
2020-01-20 17:04 ` [Intel-wired-lan] " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
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='CAJ8uoz2o0gQJOFjSsw3NEJ4vdyKfoLgj=vF3ZTj0v3bbA993qw@mail.gmail.com' \
--to=magnus.karlsson@gmail.com \
--cc=rgoodfel@isi.edu \
--cc=toke@redhat.com \
--cc=xdp-newbies@vger.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 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.