[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 07 Jul 2018 10:27:42 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: alexei.starovoitov@...il.com
Cc: jakub.kicinski@...ronome.com, daniel@...earbox.net,
saeedm@...lanox.com, saeedm@....mellanox.co.il,
alexander.h.duyck@...el.com, netdev@...r.kernel.org,
tariqt@...lanox.com, john.fastabend@...il.com, brouer@...hat.com,
borkmann@...earbox.net, peter.waskiewicz.jr@...el.com
Subject: Re: [RFC bpf-next 2/6] net: xdp: RX meta data infrastructure
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
Date: Fri, 6 Jul 2018 09:30:42 -0700
> Like doing offset rewriting at program load time similar to what we plan
> to do for tracing. Tracing programs will be doing 'task->pid' access
> and the kernel will adjust offsetof(struct task_struct, pid) during program load
> depending on BTF for the kernel.
> The same trick we can do for networking metadata.
> The program will contain load instruction md->hash that will get automatically
> adjusted to proper offset depending on BTF of 'hash' field in the NIC.
> For now I'm proposing _not_ to go that far with offset rewriting and start
> with simple steps described above.
+1
Powered by blists - more mailing lists