io threads are deprecated long time ago, not worker-handoff...

> On 27 Feb 2019, at 02:59, Zhiyong Yang <zhiyong.y...@intel.com> wrote:
> 
> Maybe I fails to understand you?
> Here is the link.
> https://lists.fd.io/g/vpp-dev/topic/vpp_io_multi_thread_model/17451337?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,17451337
>  
> <https://lists.fd.io/g/vpp-dev/topic/vpp_io_multi_thread_model/17451337?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,17451337>
>   <>
>  <>From: Damjan Marion [mailto:dmar...@me.com <mailto:dmar...@me.com>] 
> Sent: Tuesday, February 26, 2019 7:52 PM
> To: Yang, Zhiyong <zhiyong.y...@intel.com <mailto:zhiyong.y...@intel.com>>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] One question about "worker-handoff" graph node.
>  
>  
> Hmm, where I mentioned that?
>  
> 
> 
> On 26 Feb 2019, at 03:59, Zhiyong Yang <zhiyong.y...@intel.com 
> <mailto:zhiyong.y...@intel.com>> wrote:
>  
> Damjan,
>  
> As you mentioned, worker-handoff is deprecated long ago in one previous 
> email. I wonder why this working model is not strongly supported in VPP. 
> Thanks.
>  
> Zhiyong
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
> [mailto:vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>] On Behalf Of Damjan 
> Marion via Lists.Fd.Io
> Sent: Thursday, February 21, 2019 6:54 PM
> To: Yang, Zhiyong <zhiyong.y...@intel.com <mailto:zhiyong.y...@intel.com>>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] One question about "worker-handoff" graph node.
>  
>  
> It may be that just both doesn't work together, and a bit of TLC should be 
> applied...
> 
> 
> 
> On 21 Feb 2019, at 10:45, Zhiyong Yang <zhiyong.y...@intel.com 
> <mailto:zhiyong.y...@intel.com>> wrote:
>  
> Damjan,
>  
>                 Thanks for Your answer. One more question is whether 
> worker-handoff is production grade code?
>                 I have run worker-handoff for l2bd use case successfully, 
> however, the IPsec use case in transport mode fails.
> All the packets are dropped after Ethernet-input graph node is done on the 
> second worker core.
>  
> Regards
> Zhiyong
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
> [mailto:vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>] On Behalf Of Damjan 
> Marion via Lists.Fd.Io
> Sent: Wednesday, February 20, 2019 6:23 PM
> To: Yang, Zhiyong <zhiyong.y...@intel.com <mailto:zhiyong.y...@intel.com>>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] One question about "worker-handoff" graph node.
>  
>  
> 
> 
> 
> 
> On 20 Feb 2019, at 09:49, Zhiyong Yang <zhiyong.y...@intel.com 
> <mailto:zhiyong.y...@intel.com>> wrote:
>  
> Hi VPP guys,
>                 There exists a “handoff” graph node  in VPP that is named 
> “worker-handoff”. From my understanding, it looks to be  acting as a 
> distributing packets received role in the multi thread working environment , 
> and distribute pkts by hash algo to 1 or more worker threads.  Right?
>  
> y, it is basically software RSS....
> 
> 
> 
> 
> One question is that which use cases can demostrate how  the graph node is 
> applied in VPP.  If have any, please show me.
>  
> see "set interface handoff" cli...
> 
> 
> 
> 
> I know that nat also use similar handoff  cases. And if NAT is using this 
> “worker-handoff” graph node or not. If not, what’s difference between these 
> handoff graph nodes?
>  
> worker-handoff node does handoff decision based on basic l2-l3-l4 hash, nat 
> handoff node does handoff decision based on NAT session locality.
>  
> 
> 
> 
> 
>                 BTW, I mainly intend to study core to core applications by 
> this for multiple-thread working model in VPP. Appreciate your input in 
> advance.
>  
> -- 
> Damjan
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12302): https://lists.fd.io/g/vpp-dev/message/12302 
> <https://lists.fd.io/g/vpp-dev/message/12302>
> Mute This Topic: https://lists.fd.io/mt/29938708/675642 
> <https://lists.fd.io/mt/29938708/675642>
> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io>
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
> <https://lists.fd.io/g/vpp-dev/unsub>  [dmar...@me.com 
> <mailto:dmar...@me.com>]
> -=-=-=-=-=-=-=-=-=-=-=-
>  
> -- 
> Damjan
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12339): https://lists.fd.io/g/vpp-dev/message/12339 
> <https://lists.fd.io/g/vpp-dev/message/12339>
> Mute This Topic: https://lists.fd.io/mt/29938708/675642 
> <https://lists.fd.io/mt/29938708/675642>
> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io>
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
> <https://lists.fd.io/g/vpp-dev/unsub>  [dmar...@me.com 
> <mailto:dmar...@me.com>]
> -=-=-=-=-=-=-=-=-=-=-=-
>  
> -- 
> Damjan
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#12349): https://lists.fd.io/g/vpp-dev/message/12349 
> <https://lists.fd.io/g/vpp-dev/message/12349>
> Mute This Topic: https://lists.fd.io/mt/29938708/675642 
> <https://lists.fd.io/mt/29938708/675642>
> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io>
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
> <https://lists.fd.io/g/vpp-dev/unsub>  [dmar...@me.com 
> <mailto:dmar...@me.com>]
> -=-=-=-=-=-=-=-=-=-=-=-

-- 
Damjan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12350): https://lists.fd.io/g/vpp-dev/message/12350
Mute This Topic: https://lists.fd.io/mt/29938708/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to