From: Jiri Pirko <jiri@resnulli•us>
To: "Maciej Żenczykowski" <zenczykowski@gmail•com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail•com>,
Thomas Graf <tgraf@suug•ch>,
John Fastabend <john.fastabend@gmail•com>,
Jakub Kicinski <kubakici@wp•pl>,
Linux NetDev <netdev@vger•kernel.org>,
David Miller <davem@davemloft•net>,
Jamal Hadi Salim <jhs@mojatatu•com>,
roopa@cumulusnetworks•com, simon.horman@netronome•com,
ast@kernel•org, daniel@iogearbox•net, prem@barefootnetworks•com,
Hannes Frederic Sowa <hannes@stressinduktion•org>,
Jiri Benc <jbenc@redhat•com>, Tom Herbert <tom@herbertland•com>,
mattyk@mellanox•com, idosch@mellanox•com, eladr@mellanox•com,
yotamg@mellanox•com, nogahf@mellanox•com, ogerlitz@mellanox•com,
"John W. Linville" <linville@tuxdriver•com>,
Andy Gospodarek <andy@greyhouse•net>,
Florian Fainelli <f.fainelli@gmail•com>,
dsa@c
Subject: Re: Let's do P4
Date: Mon, 31 Oct 2016 08:47:51 +0100 [thread overview]
Message-ID: <20161031074751.GA1679@nanopsycho.orion> (raw)
In-Reply-To: <CAHo-Ooz82uFsf6F=pU-jrR-KOADWuRmkiAfKaB_sQGc=4N7z4g@mail.gmail.com>
Mon, Oct 31, 2016 at 07:03:53AM CET, zenczykowski@gmail•com wrote:
>One thing to consider...
>
>Just because the compiler could be in the kernel, doesn't mean it has to be.
>
>One could envision a hotplug/modprobe like helper program that the
>kernel executes
>when it wants to translate from one encoding (say p4) to another (say [e]bpf).
>
>This keeps complexity (compiler) out of the kernel, while still
>allowing us to have
>the illusion of only one interface to sw/hw. And it has the nice
>benefit of allowing us
>to use existing compiler toolchains...
This idea was repeatedly marked as unacceptable.
next prev parent reply other threads:[~2016-10-31 7:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 7:53 Let's do P4 Jiri Pirko
2016-10-29 9:39 ` Thomas Graf
2016-10-29 10:10 ` Jiri Pirko
2016-10-29 11:15 ` Thomas Graf
2016-10-29 11:28 ` Jiri Pirko
2016-10-29 12:09 ` Thomas Graf
2016-10-29 13:58 ` Jiri Pirko
2016-10-29 14:54 ` Jakub Kicinski
2016-10-29 14:58 ` Jiri Pirko
2016-10-29 14:49 ` Jakub Kicinski
2016-10-29 14:55 ` Jiri Pirko
2016-10-29 16:46 ` John Fastabend
2016-10-30 7:44 ` Jiri Pirko
2016-10-30 10:26 ` Thomas Graf
2016-10-30 16:38 ` Jiri Pirko
2016-10-30 17:45 ` Jakub Kicinski
2016-10-30 18:01 ` Jiri Pirko
2016-10-30 18:44 ` Jakub Kicinski
2016-10-30 19:56 ` Jiri Pirko
2016-10-30 21:14 ` John Fastabend
2016-10-30 22:39 ` Alexei Starovoitov
2016-10-31 6:03 ` Maciej Żenczykowski
2016-10-31 7:47 ` Jiri Pirko [this message]
2016-10-31 9:39 ` Jiri Pirko
2016-10-31 16:53 ` John Fastabend
2016-10-31 17:12 ` Jiri Pirko
2016-10-31 18:32 ` Hannes Frederic Sowa
2016-10-31 19:35 ` John Fastabend
2016-11-01 8:46 ` Jiri Pirko
2016-11-01 15:13 ` John Fastabend
2016-11-02 8:07 ` Jiri Pirko
2016-11-02 15:18 ` John Fastabend
2016-11-02 15:23 ` Jiri Pirko
2016-11-02 2:29 ` Daniel Borkmann
2016-11-02 5:06 ` Maciej Żenczykowski
2016-11-02 8:14 ` Jiri Pirko
2016-11-02 15:22 ` John Fastabend
2016-11-02 15:27 ` Jiri Pirko
2016-10-30 20:54 ` John Fastabend
2016-11-01 11:57 ` Jamal Hadi Salim
2016-11-01 15:03 ` John Fastabend
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=20161031074751.GA1679@nanopsycho.orion \
--to=jiri@resnulli$(echo .)us \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=andy@greyhouse$(echo .)net \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dsa@c \
--cc=eladr@mellanox$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=idosch@mellanox$(echo .)com \
--cc=jbenc@redhat$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kubakici@wp$(echo .)pl \
--cc=linville@tuxdriver$(echo .)com \
--cc=mattyk@mellanox$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nogahf@mellanox$(echo .)com \
--cc=ogerlitz@mellanox$(echo .)com \
--cc=prem@barefootnetworks$(echo .)com \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=simon.horman@netronome$(echo .)com \
--cc=tgraf@suug$(echo .)ch \
--cc=tom@herbertland$(echo .)com \
--cc=yotamg@mellanox$(echo .)com \
--cc=zenczykowski@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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