On Thu, Jan 2, 2020 at 6:35 PM Andrew Rybchenko
wrote:
>
> Somnath,
>
> On 12/31/19 5:15 AM, Somnath Kotur wrote:
> > Andrew,
> >
> > On Tue, Dec 24, 2019 at 3:23 PM Andrew Rybchenko
> > wrote:
> >> On 12/24/19 6:16 AM, Somnath Kotur wrote:
> >>> Given that we haven't heard any objection from any
Somnath,
On 12/31/19 5:15 AM, Somnath Kotur wrote:
> Andrew,
>
> On Tue, Dec 24, 2019 at 3:23 PM Andrew Rybchenko
> wrote:
>> On 12/24/19 6:16 AM, Somnath Kotur wrote:
>>> Given that we haven't heard any objection from anyone in a while on
>>> this ...can we get this in please?
>> I'm sorry, but
Hi Olivier,
On 12/27/19 5:50 PM, Olivier Matz wrote:
> Hi,
>
> On Tue, Dec 24, 2019 at 12:53:21PM +0300, Andrew Rybchenko wrote:
>> On 12/24/19 6:16 AM, Somnath Kotur wrote:
>>> Given that we haven't heard any objection from anyone in a while on
>>> this ...can we get this in please?
>> I'm sorry,
Andrew,
On Tue, Dec 24, 2019 at 3:23 PM Andrew Rybchenko
wrote:
>
> On 12/24/19 6:16 AM, Somnath Kotur wrote:
> > Given that we haven't heard any objection from anyone in a while on
> > this ...can we get this in please?
>
> I'm sorry, but have you seen below?
> It means that PKT_RX_QINQ_STRIPPED
On Fri, Dec 27, 2019 at 8:20 PM Olivier Matz wrote:
>
> Hi,
>
> On Tue, Dec 24, 2019 at 12:53:21PM +0300, Andrew Rybchenko wrote:
> > On 12/24/19 6:16 AM, Somnath Kotur wrote:
> > > Given that we haven't heard any objection from anyone in a while on
> > > this ...can we get this in please?
> >
> >
Hi,
On Tue, Dec 24, 2019 at 12:53:21PM +0300, Andrew Rybchenko wrote:
> On 12/24/19 6:16 AM, Somnath Kotur wrote:
> > Given that we haven't heard any objection from anyone in a while on
> > this ...can we get this in please?
>
> I'm sorry, but have you seen below?
> It means that PKT_RX_QINQ_STRI
On 12/24/19 6:16 AM, Somnath Kotur wrote:
> Given that we haven't heard any objection from anyone in a while on
> this ...can we get this in please?
I'm sorry, but have you seen below?
It means that PKT_RX_QINQ_STRIPPED, PKT_RX_QINQ, PKT_RX_VLAN
and PKT_RX_VLAN_STRIPPED must be clarified.
It soun
Given that we haven't heard any objection from anyone in a while on
this ...can we get this in please?
Thanks
On Mon, Dec 16, 2019 at 2:43 PM Andrew Rybchenko
wrote:
>
> On 12/16/19 11:47 AM, Somnath Kotur wrote:
> > On Mon, Dec 16, 2019 at 12:01 PM Andrew Rybchenko
> > wrote:
> >>
> >> On 12/1
On 12/16/19 11:47 AM, Somnath Kotur wrote:
> On Mon, Dec 16, 2019 at 12:01 PM Andrew Rybchenko
> wrote:
>>
>> On 12/16/19 6:16 AM, Somnath Kotur wrote:
>>> Certain hardware may be able to strip and/or save only the outermost
>>> VLAN instead of both the VLANs in the mbuf in a QinQ scenario.
>>> To
On Mon, Dec 16, 2019 at 12:01 PM Andrew Rybchenko
wrote:
>
> On 12/16/19 6:16 AM, Somnath Kotur wrote:
> > Certain hardware may be able to strip and/or save only the outermost
> > VLAN instead of both the VLANs in the mbuf in a QinQ scenario.
> > To handle such cases, we could re-interpret setting
On 12/16/19 6:16 AM, Somnath Kotur wrote:
> Certain hardware may be able to strip and/or save only the outermost
> VLAN instead of both the VLANs in the mbuf in a QinQ scenario.
> To handle such cases, we could re-interpret setting of just
> PKT_RX_QINQ_STRIPPED
> to indicate that only the outermo
Certain hardware may be able to strip and/or save only the outermost
VLAN instead of both the VLANs in the mbuf in a QinQ scenario.
To handle such cases, we could re-interpret setting of just PKT_RX_QINQ_STRIPPED
to indicate that only the outermost VLAN has been stripped by the hardware and
saved i
12 matches
Mail list logo
