On Wed, Nov 13, 2019 at 12:54 PM Pravin Shelar wrote:
>
> On Tue, Nov 12, 2019 at 7:09 AM wrote:
> >
> > From: Tonghao Zhang
> >
> > When using the kernel datapath, the upcall don't
> > include skb hash info relatived. That will introduce
> > some problem, because the hash of skb is important
>
On Tue, Nov 12, 2019 at 7:09 AM wrote:
>
> From: Tonghao Zhang
>
> When using the kernel datapath, the upcall don't
> include skb hash info relatived. That will introduce
> some problem, because the hash of skb is important
> in kernel stack. For example, VXLAN module uses
> it to select UDP src
On Wed, Nov 13, 2019 at 2:06 AM Gregory Rose wrote:
>
>
> On 11/12/2019 7:08 AM, xiangxia.m@gmail.com wrote:
> > From: Tonghao Zhang
> >
> > When using the kernel datapath, the upcall don't
> > include skb hash info relatived. That will introduce
> > some problem, because the hash of skb is
On 11/12/2019 7:08 AM, xiangxia.m@gmail.com wrote:
From: Tonghao Zhang
When using the kernel datapath, the upcall don't
include skb hash info relatived. That will introduce
some problem, because the hash of skb is important
in kernel stack. For example, VXLAN module uses
it to select UDP
From: Tonghao Zhang
When using the kernel datapath, the upcall don't
include skb hash info relatived. That will introduce
some problem, because the hash of skb is important
in kernel stack. For example, VXLAN module uses
it to select UDP src port. The tx queue selection
may also use the hash in
