Yes, I want to split traffic between two applications via classifier. The use
case look like this:
++++> eth0 +++> Parser +++> Classifier +++> Separate Queues/Pools for App 1
---> Scheduler ---> Worker threads(Packets Processing) ---> Egress Queues for
App 1 ++++++> Tx Scheduler ++> Shaper++>eth0
+
+
+
+
++++++++> Separate Queues/Pools for App 2 --->
Scheduler ---> Worker threads (Packets Processing) ----> Egress Queues for App
2 ++++
Parser/Classifier/Tx Scheduler/Traffic Shaper will be shared by two data plane
applications while the other ODP items (Pool/Queue/Scheduler) are private.
BR / Jianhua
-----Original Message-----
From: Taras Kondratiuk [mailto:[email protected]]
Sent: 2015年4月4日 0:31
To: Zhujianhua; Jerin Jacob
Cc: [email protected]
Subject: Re: [lng-odp] NO ODP API for Packet classification and Packet Shaping
On 03/30/2015 03:34 PM, Zhujianhua wrote:
> @ Jerin Jacob:
> What will happen if odp_cos_set_pool(odp_cos_t cos_id, odp_buffer_pool_t
> pool_id) was called twice?
> Will the new pool_id replace the old one or the CoS have two pools?
>
> @Taras:
> Assume: set several pools per pktio interface.
> What will happen if two data plane applications share one physical Ethernet
> port to receive packets?
> Since the pool is per pktio interface, will these two applications share the
> same buffer pool?
> If there is memory leak in one application, the other application will be
> disturbed.
> Correct me if my understanding were wrong.
That's a nice question. I'm afraid this use-case was not considered before.
Do you want to split traffic between two applications via classifier?
>
> Maybe to let each CoS have more than one pool and limit the max number of
> Pool to for example 4 (Let the application designer decide how many pools are
> needed for each CoS) could be one option.
That is a possible solution.
_______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
