Re: [PATCH v7 net-next 00/18] Introducing P4TC
From: Daniel Borkmann <daniel@iogearbox.net>
Date: 2023-10-17 16:06:12
On 10/17/23 5:57 PM, Jamal Hadi Salim wrote:
On Tue, Oct 17, 2023 at 11:54 AM Daniel Borkmann [off-list ref] wrote:quoted
On 10/17/23 5:38 PM, Jamal Hadi Salim wrote:quoted
On Tue, Oct 17, 2023 at 11:00 AM Daniel Borkmann [off-list ref] wrote:quoted
On 10/16/23 10:38 PM, Jamal Hadi Salim wrote:quoted
On Mon, Oct 16, 2023 at 4:15 PM Jakub Kicinski [off-list ref] wrote:[...]quoted
quoted
FWIW please do not post another version this week (not that I think that you would do that, but better safe than sorry. Last week the patch bombs pushed the shared infra 24h+ behind the list..)Not intending to.Given bpf & kfuncs, please also Cc bpf@vger.kernel.org on future revisions as not everyone on bpf list is subscribed to netdev.I thought i did that, maybe it was in earlier patches. Do you want Cc on everything or only on kfuncs? I am getting conflicting messages, do you have to Cc bpf for kfuncs? Example, attached from (some fs?) conference last month i thinkThis is extending capabilities of XDP and tc BPF prog types, so yes, the bpf list should be in the loop.Roger that, makes sense. So all patches or only kfunc ones?
Preferably the whole series as it's a bit hard to see some end to end example on how it would be used if it's largely taken out of context.