RE: [EXT] Re: l2/l3_len fields

2022-01-25 Thread Liron Himi
-Original Message- From: Stephen Hemminger Sent: Tuesday, 25 January 2022 23:25 To: Liron Himi Cc: dev@dpdk.org Subject: Re: [EXT] Re: l2/l3_len fields On Tue, 25 Jan 2022 17:38:42 + Liron Himi wrote: > -Original Message- > From: Stephen Hemminger > Sent: M

Re: [EXT] Re: l2/l3_len fields

2022-01-25 Thread Stephen Hemminger
On Tue, 25 Jan 2022 17:38:42 + Liron Himi wrote: > -Original Message- > From: Stephen Hemminger > Sent: Monday, 24 January 2022 19:21 > To: Liron Himi > Cc: dev@dpdk.org > Subject: [EXT] Re: l2/l3_len fields &

RE: [EXT] Re: l2/l3_len fields

2022-01-25 Thread Liron Himi
-Original Message- From: Stephen Hemminger Sent: Monday, 24 January 2022 19:21 To: Liron Himi Cc: dev@dpdk.org Subject: [EXT] Re: l2/l3_len fields External Email -- On Mon, 24 Jan 2022 08:39:59 + Liron Himi

Re: l2/l3_len fields

2022-01-24 Thread Stephen Hemminger
On Mon, 24 Jan 2022 08:39:59 + Liron Himi wrote: > Hi, > > > > Can you please share the motivation of not filling l2/l3-len fields on PMD's > RX function? > > PMD already filling the mbuf with parsing info, and the l2/l3-len are also > probably part of the HW descriptor, so why no propa