All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "bpf\@ietf.org" <bpf@ietf.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] IETF BPF working group draft charter
Date: Wed, 31 May 2023 15:38:10 -0400	[thread overview]
Message-ID: <9539.1685561890@dyas> (raw)
In-Reply-To: <ZHbDekB0KderhSTl@infradead.org>


[-- Attachment #1.1: Type: text/plain, Size: 472 bytes --]


I assume that one use cases is where a VM (windows or Linux inside) does a
eBPF (XDP) load into a virtual network interface, and the hypervisor manages
to push that down to some engine in a physical card.

In that case, we might have mixes of Windows, Linux and network card
implementations of eBPF on the same "transaction" path.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*




[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

[-- Attachment #2: Type: text/plain, Size: 76 bytes --]

-- 
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf

WARNING: multiple messages have this Message-ID (diff)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "bpf\@ietf.org" <bpf@ietf.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [Bpf] IETF BPF working group draft charter
Date: Wed, 31 May 2023 15:38:10 -0400	[thread overview]
Message-ID: <9539.1685561890@dyas> (raw)
Message-ID: <20230531193810.PCB5iaIv9ONUtY36ogyc6nBbmgsd7w-7rFAKt62yJho@z> (raw)
In-Reply-To: <ZHbDekB0KderhSTl@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]


I assume that one use cases is where a VM (windows or Linux inside) does a
eBPF (XDP) load into a virtual network interface, and the hypervisor manages
to push that down to some engine in a physical card.

In that case, we might have mixes of Windows, Linux and network card
implementations of eBPF on the same "transaction" path.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

  reply	other threads:[~2023-05-31 19:43 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH7PR21MB38780769D482CC5F83768D3CA37E9@PH7PR21MB3878.namprd21.prod.outlook.com>
     [not found] ` <87v8grkn67.fsf@gnu.org>
2023-05-17 18:19   ` [Bpf] IETF BPF working group draft charter Dave Thaler
2023-05-17 18:19     ` Dave Thaler
2023-05-17 21:00     ` David Vernet
2023-05-17 21:00       ` David Vernet
2023-05-17 21:13       ` Dave Thaler
2023-05-17 21:13         ` Dave Thaler
2023-05-18 17:33     ` Jose E. Marchesi
2023-05-18 17:33       ` Jose E. Marchesi
2023-05-18 19:42       ` Dave Thaler
2023-05-18 19:42         ` Dave Thaler
2023-05-23 16:32         ` David Vernet
2023-05-23 16:32           ` David Vernet
2023-05-23 16:50           ` Dave Thaler
2023-05-23 16:50             ` Dave Thaler
2023-05-23 17:15             ` David Vernet
2023-05-23 17:15               ` David Vernet
2023-05-23 19:08               ` David Vernet
2023-05-23 19:08                 ` David Vernet
2023-05-23 19:42                 ` Erik Kline
2023-05-23 19:42                   ` Erik Kline
2023-05-23 19:47                   ` Jose E. Marchesi
2023-05-23 19:47                     ` Jose E. Marchesi
2023-05-23 17:58           ` Michael Richardson
2023-05-23 17:58             ` Michael Richardson
2023-05-23 18:25             ` Dave Thaler
2023-05-23 18:25               ` Dave Thaler
2023-05-23 20:28             ` David Vernet
2023-05-23 20:28               ` David Vernet
2023-05-24 20:38               ` Suresh Krishnan
2023-05-24 21:06                 ` Jose E. Marchesi
2023-05-24 21:06                   ` Jose E. Marchesi
2023-05-26 16:05                   ` Dave Thaler
2023-05-26 16:05                     ` Dave Thaler
2023-05-26 17:25                     ` Jose E. Marchesi
2023-05-26 17:25                       ` Jose E. Marchesi
2023-05-25  7:44               ` Christoph Hellwig
2023-05-25  7:44                 ` Christoph Hellwig
2023-05-25 10:14                 ` Jose E. Marchesi
2023-05-25 10:14                   ` Jose E. Marchesi
2023-05-26 16:02                   ` Dave Thaler
2023-05-26 16:02                     ` Dave Thaler
2023-05-26 16:55                     ` David Vernet
2023-05-26 16:55                       ` David Vernet
2023-05-26 17:01                       ` Dave Thaler
2023-05-26 17:01                         ` Dave Thaler
2023-05-26 17:19                         ` David Vernet
2023-05-26 17:19                           ` David Vernet
2023-05-26 17:30                           ` Dave Thaler
2023-05-26 17:30                             ` Dave Thaler
2023-05-31  3:48                             ` Christoph Hellwig
2023-05-31  3:48                               ` Christoph Hellwig
2023-05-31 19:38                               ` Michael Richardson [this message]
2023-05-31 19:38                                 ` Michael Richardson
2023-05-31 19:44                                 ` Dave Thaler
2023-05-31 19:44                                   ` Dave Thaler
2023-06-01 17:40                                   ` Michael Richardson
2023-06-01 17:40                                     ` Michael Richardson
2023-05-31  3:47                         ` Christoph Hellwig
2023-05-31  3:47                           ` Christoph Hellwig

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=9539.1685561890@dyas \
    --to=mcr+ietf@sandelman.ca \
    --cc=bpf@ietf.org \
    --cc=bpf@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.