On 29/04/15 18:19, Ola Liljedahl wrote:
On 29 April 2015 at 18:14, Zoltan Kiss <[email protected]
<mailto:[email protected]>> wrote:
It doesn't apply to api-next. Anyway, I've sent an implementation,
see "[API-NEXT PATCH] packet: implement optional parsing". But if we
go with Ola's idea, it won't be needed.
Actually Bill's idea.
If parsing is made lazy, where do you have to check whether to actually
perform the parsing? Hopefully we don't need a check in every
odp_packet_has_xxx() call. If the application is using the
odp_packet_flags.h API, is there some call which always will be called
(and called first) which can trigger the parsing? E.g.
odp_packet_has_error() could check whether parsing has been done and if
not do the parsing. Other calls may not have to perform the check. Would
such a design be robust enough?
I don't think it is mandated now that any of these calls are made first.
And it would be error prone to mandate that, app developers can forget
about it easily.
You would need to put this condition check in every odp_packet_has_xxx()
call. But I guess branch predictors can sort that out for a software
implementation.
On 29/04/15 07:45, Savolainen, Petri (Nokia - FI/Espoo) wrote:
It's (v2) on the list (since last Thu):
[lng-odp] [API-NEXT PATCH v2 4/5] api: packet_io: added parse mode
-Petri
_______________________________________________
lng-odp mailing list
[email protected] <mailto:[email protected]>
https://lists.linaro.org/mailman/listinfo/lng-odp
_______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
