From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "Brian G. Merrell" <brian.g.merrell@gmail.com>
Cc: xdp-newbies@vger.kernel.org,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Maciej Żenczykowski" <maze@google.com>,
"Lorenz Bauer" <lmb@cloudflare.com>,
"Andrey Ignatov" <rdna@fb.com>,
bpf@vger.kernel.org
Subject: Re: How to orchestrate multiple XDP programs
Date: Wed, 16 Dec 2020 13:45:17 +0100 [thread overview]
Message-ID: <873605din6.fsf@toke.dk> (raw)
In-Reply-To: <20201216072920.hh42kxb5voom4aau@snout.localdomain>
"Brian G. Merrell" <brian.g.merrell@gmail.com> writes:
> Yes, please, if anyone has additional thoughts please weigh in, but I
> think my team is ready to commit to option #2.
>
> Any concerns about my assessment and request?
Just a quick note - since the holidays are fast approaching I won't have
time to do anything more about it before January anyway. But until then,
thank you for volunteering to do the Go implementation work!
I'll write up the "spec" once I'm back from the holidays, and we can
continue the discussion (and you can start prototyping an
implementation). And if you run away screaming after seeing the gory
details we can of course reconsider ;)
Sounds good?
And if someone else chimes in with opinions before or during that, great!
-Toke
next prev parent reply other threads:[~2020-12-16 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201201091203.ouqtpdmvvl2m2pga@snout.localdomain>
2020-12-01 12:08 ` How to orchestrate multiple XDP programs Toke Høiland-Jørgensen
2020-12-16 7:29 ` Brian G. Merrell
2020-12-16 12:45 ` Toke Høiland-Jørgensen [this message]
[not found] ` <87tur0x874.fsf@toke.dk>
2021-02-10 22:27 ` Brian G. Merrell
2021-02-11 11:18 ` Toke Høiland-Jørgensen
2021-02-12 6:51 ` Brian G. Merrell
2021-02-15 12:47 ` Toke Høiland-Jørgensen
2021-02-17 1:20 ` Brian G. Merrell
2021-02-17 15:53 ` Toke Høiland-Jørgensen
2021-02-17 22:27 ` Brian G. Merrell
2021-02-18 16:20 ` Toke Høiland-Jørgensen
2021-02-22 19:34 ` Brian G. Merrell
2021-02-22 22:41 ` Toke Høiland-Jørgensen
2021-02-23 8:54 ` Brian G. Merrell
2021-02-23 11:07 ` Toke Høiland-Jørgensen
2021-02-18 10:16 ` Brian G. Merrell
2021-02-18 11:00 ` Toke Høiland-Jørgensen
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=873605din6.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=brian.g.merrell@gmail.com \
--cc=brouer@redhat.com \
--cc=lmb@cloudflare.com \
--cc=maze@google.com \
--cc=rdna@fb.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 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).