Re: [PATCH net-next] erspan: set bso bit based on mirrored packet's len

2018-05-17 Thread William Tu
On Wed, May 16, 2018 at 3:24 PM, Tobin C. Harding wrote: > On Wed, May 16, 2018 at 07:05:34AM -0700, William Tu wrote: >> On Mon, May 14, 2018 at 10:33 PM, Tobin C. Harding >> wrote: >> > On Mon, May 14, 2018 at 04:54:36PM -0700, William Tu wrote: >> >>

Re: [PATCH net-next] erspan: set bso bit based on mirrored packet's len

2018-05-16 Thread Tobin C. Harding
On Wed, May 16, 2018 at 07:05:34AM -0700, William Tu wrote: > On Mon, May 14, 2018 at 10:33 PM, Tobin C. Harding wrote: > > On Mon, May 14, 2018 at 04:54:36PM -0700, William Tu wrote: > >> Before the patch, the erspan BSO bit (Bad/Short/Oversized) is not > >> handled. BSO has

Re: [PATCH net-next] erspan: set bso bit based on mirrored packet's len

2018-05-16 Thread William Tu
On Mon, May 14, 2018 at 10:33 PM, Tobin C. Harding wrote: > On Mon, May 14, 2018 at 04:54:36PM -0700, William Tu wrote: >> Before the patch, the erspan BSO bit (Bad/Short/Oversized) is not >> handled. BSO has 4 possible values: >> 00 --> Good frame with no error, or unknown

Re: [PATCH net-next] erspan: set bso bit based on mirrored packet's len

2018-05-14 Thread Tobin C. Harding
On Mon, May 14, 2018 at 04:54:36PM -0700, William Tu wrote: > Before the patch, the erspan BSO bit (Bad/Short/Oversized) is not > handled. BSO has 4 possible values: > 00 --> Good frame with no error, or unknown integrity > 11 --> Payload is a Bad Frame with CRC or Alignment Error > 01 -->