On Thu, 7 Jul 2016 15:18:11 +0000, Fastabend, John R wrote:
The other interesting thing would be to do more than just packetYes!
At the XDP summit we were discussing pipe-lining XDP programs in
general, with different stages of the pipeline potentially using
specific hardware capabilities or even being directly mappable on
fixed HW functions.
Designating parsing as one of specialized blocks makes sense in a long
run, probably at the first stage with recirculation possible. We also
have some parsing HW we could utilize at some point. However, I'm
worried that it's too early to impose constraints and APIs. I agree
that we should first set a standard way to pass metadata across tail
calls to facilitate any form of pipe lining, regardless of which parts
of pipeline HW is able to offload.