On 04/07/2015 08:16 PM, Rosenboim, Leonid wrote:
Taras,
I have seen similar limitations on other platforms,
and in my opinion, the solution could be to simply decouple the
odp_queue_t identifier from the HW queue number, and have each
odp_queue_t identify a table entry, which contains a HW queue number,
which can be changed by the implementation without application knowledge
when it is necessary.
From another point of view, the odp_queue_t when initially created will
not be associated with a real HW queue, until it is assigned to a CoS,
at which point it is assigned with the hardware resources needed to pass
traffic. An odp_queue_t that of the PKTIN type will not be able to pass traffic
until it is assigned a CoS source anyway.
Sorry, I've missed this reply.
odp_queue_t is decoupled from HW queue. Implicitly changing HW queue
was my first idea, but it actually doesn't work, because the same
odp_queue_t can be used in several places (e.g. connected to two CoSes).
_______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
