On 6/2/2021 1:46 PM, Ilya Maximets wrote:
> On 6/1/21 4:28 PM, Ivan Malov wrote:
>> Hi Ilya,
>>
>> Thank you for reviewing the proposal at such short notice. I'm afraid that
>> prior discussions overlook the simple fact that the whole problem is not
>> limited to just VF representors. Action PORT
On 6/8/21 9:49 PM, Thomas Monjalon wrote:
> 08/06/2021 18:32, Andrew Rybchenko:
>> On 6/8/21 7:13 PM, Thomas Monjalon wrote:
>>> We will be at least 4 tomorrow Wednesday 3pm UTC.
>>> Everybody is welcome to join the community meeting:
>>> https://zoom.us/j/93391811485
>> Invite has July, 7. Typ
08/06/2021 18:32, Andrew Rybchenko:
> On 6/8/21 7:13 PM, Thomas Monjalon wrote:
> > We will be at least 4 tomorrow Wednesday 3pm UTC.
> > Everybody is welcome to join the community meeting:
> > https://zoom.us/j/93391811485
>
> Invite has July, 7. Typo?
Yes was a typo, sorry.
The invite was u
On 6/8/21 7:13 PM, Thomas Monjalon wrote:
> 07/06/2021 18:07, Thomas Monjalon:
>> 07/06/2021 15:21, Ilya Maximets:
>>> On 6/7/21 2:08 PM, Ori Kam wrote:
From: Andrew Rybchenko
> On 6/7/21 11:28 AM, Thomas Monjalon wrote:
>> I see emails don't work well to conclude on how to manage rep
07/06/2021 18:07, Thomas Monjalon:
> 07/06/2021 15:21, Ilya Maximets:
> > On 6/7/21 2:08 PM, Ori Kam wrote:
> > > From: Andrew Rybchenko
> > >> On 6/7/21 11:28 AM, Thomas Monjalon wrote:
> > >>> I see emails don't work well to conclude on how to manage representors.
> > >>> I propose working in li
On 07/06/2021 22:27, Ilya Maximets wrote:
On 6/3/21 1:29 PM, Ivan Malov wrote:
On 03/06/2021 12:29, Ilya Maximets wrote:
On 6/2/21 9:35 PM, Ivan Malov wrote:
On 02/06/2021 20:35, Ilya Maximets wrote:
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason:
On 6/3/21 1:29 PM, Ivan Malov wrote:
> On 03/06/2021 12:29, Ilya Maximets wrote:
>> On 6/2/21 9:35 PM, Ivan Malov wrote:
>>> On 02/06/2021 20:35, Ilya Maximets wrote:
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason: "Recipient address rejected:
07/06/2021 15:21, Ilya Maximets:
> On 6/7/21 2:08 PM, Ori Kam wrote:
> > From: Andrew Rybchenko
> >> On 6/7/21 11:28 AM, Thomas Monjalon wrote:
> >>> I see emails don't work well to conclude on how to manage representors.
> >>> I propose working in live meetings so we can try to align our views on
On 6/7/21 2:08 PM, Ori Kam wrote:
>
>
>> -Original Message-
>> From: Andrew Rybchenko
>> semantics
>>
>> On 6/7/21 11:28 AM, Thomas Monjalon wrote:
>>> 03/06/2021 11:55, Andrew Rybchenko:
On 6/3/21 12:18 PM, Ori Kam wrote:
> Sorry but OVS got it right, this is the idea to send p
> -Original Message-
> From: Andrew Rybchenko
> semantics
>
> On 6/7/21 11:28 AM, Thomas Monjalon wrote:
> > 03/06/2021 11:55, Andrew Rybchenko:
> >> On 6/3/21 12:18 PM, Ori Kam wrote:
> >>> Sorry but OVS got it right, this is the idea to send packet to the
> >>> VF not to the represent
On 6/7/21 11:28 AM, Thomas Monjalon wrote:
> 03/06/2021 11:55, Andrew Rybchenko:
>> On 6/3/21 12:18 PM, Ori Kam wrote:
>>> Sorry but OVS got it right, this is the idea to send packet to the VF not
>>> to the representor,
>>> I think that our first discussion should be what is a representor,
>>> I
03/06/2021 11:55, Andrew Rybchenko:
> On 6/3/21 12:18 PM, Ori Kam wrote:
> > Sorry but OVS got it right, this is the idea to send packet to the VF not
> > to the representor,
> > I think that our first discussion should be what is a representor,
> > I know that there are a lot threads about it bu
On 03/06/2021 12:29, Ilya Maximets wrote:
On 6/2/21 9:35 PM, Ivan Malov wrote:
On 02/06/2021 20:35, Ilya Maximets wrote:
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason: "Recipient address rejected: Domain not found."
Please, try to ad them back on r
On 6/3/21 12:33 PM, Andrew Rybchenko wrote:
> On 6/3/21 12:29 PM, Ilya Maximets wrote:
>> On 6/2/21 9:35 PM, Ivan Malov wrote:
>>> On 02/06/2021 20:35, Ilya Maximets wrote:
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason: "Recipient address rej
On 6/3/21 12:29 PM, Ilya Maximets wrote:
> On 6/2/21 9:35 PM, Ivan Malov wrote:
>> On 02/06/2021 20:35, Ilya Maximets wrote:
>>> (Dropped Broadcom folks from CC. Mail server refuses to accept their
>>> emails for some reason: "Recipient address rejected: Domain not found."
>>> Please, try to ad th
On 6/3/21 12:18 PM, Ori Kam wrote:
> Hi All,
>
>> -Original Message-
>> From: Ivan Malov
>>
>> On 02/06/2021 14:21, Eli Britstein wrote:
>>>
>>> On 6/2/2021 1:50 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/2/21 12:57 PM, El
On 6/2/21 9:35 PM, Ivan Malov wrote:
> On 02/06/2021 20:35, Ilya Maximets wrote:
>> (Dropped Broadcom folks from CC. Mail server refuses to accept their
>> emails for some reason: "Recipient address rejected: Domain not found."
>> Please, try to ad them back on reply.)
>>
>> On 6/2/21 6:26 PM, And
Hi All,
> -Original Message-
> From: Ivan Malov
>
> On 02/06/2021 14:21, Eli Britstein wrote:
> >
> > On 6/2/2021 1:50 PM, Andrew Rybchenko wrote:
> >> External email: Use caution opening links or attachments
> >>
> >>
> >> On 6/2/21 12:57 PM, Eli Britstein wrote:
> >>> On 6/1/2021 5:53
On 02/06/2021 20:35, Ilya Maximets wrote:
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason: "Recipient address rejected: Domain not found."
Please, try to ad them back on reply.)
On 6/2/21 6:26 PM, Andrew Rybchenko wrote:
On 6/2/21 3:46 PM, Ilya Maxim
(Dropped Broadcom folks from CC. Mail server refuses to accept their
emails for some reason: "Recipient address rejected: Domain not found."
Please, try to ad them back on reply.)
On 6/2/21 6:26 PM, Andrew Rybchenko wrote:
> On 6/2/21 3:46 PM, Ilya Maximets wrote:
>> On 6/1/21 4:28 PM, Ivan Malov
On 6/2/21 3:46 PM, Ilya Maximets wrote:
> On 6/1/21 4:28 PM, Ivan Malov wrote:
>> Hi Ilya,
>>
>> Thank you for reviewing the proposal at such short notice. I'm afraid that
>> prior discussions overlook the simple fact that the whole problem is not
>> limited to just VF representors. Action PORT_I
On 6/2/21 3:16 PM, Thomas Monjalon wrote:
> 01/06/2021 14:10, Ilya Maximets:
>> On 6/1/21 1:14 PM, Ivan Malov wrote:
>>> By its very name, action PORT_ID means that packets hit an ethdev with the
>>> given DPDK port ID. At least the current comments don't state the opposite.
>>> That said, since po
On 6/2/21 2:16 PM, Thomas Monjalon wrote:
> 01/06/2021 14:10, Ilya Maximets:
>> On 6/1/21 1:14 PM, Ivan Malov wrote:
>>> By its very name, action PORT_ID means that packets hit an ethdev with the
>>> given DPDK port ID. At least the current comments don't state the opposite.
>>> That said, since po
On 6/1/21 4:28 PM, Ivan Malov wrote:
> Hi Ilya,
>
> Thank you for reviewing the proposal at such short notice. I'm afraid that
> prior discussions overlook the simple fact that the whole problem is not
> limited to just VF representors. Action PORT_ID is also used with respect to
> the admin PF
On 02/06/2021 14:21, Eli Britstein wrote:
On 6/2/2021 1:50 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/2/21 12:57 PM, Eli Britstein wrote:
On 6/1/2021 5:53 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On
01/06/2021 14:10, Ilya Maximets:
> On 6/1/21 1:14 PM, Ivan Malov wrote:
> > By its very name, action PORT_ID means that packets hit an ethdev with the
> > given DPDK port ID. At least the current comments don't state the opposite.
> > That said, since port representors had been adopted, application
On 6/2/21 2:21 PM, Eli Britstein wrote:
>
> On 6/2/2021 1:50 PM, Andrew Rybchenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 6/2/21 12:57 PM, Eli Britstein wrote:
>>> On 6/1/2021 5:53 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or
On 6/2/2021 1:50 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/2/21 12:57 PM, Eli Britstein wrote:
On 6/1/2021 5:53 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/1/21 5:44 PM, Eli Britstein wrote:
On
On 6/2/21 12:57 PM, Eli Britstein wrote:
>
> On 6/1/2021 5:53 PM, Andrew Rybchenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 6/1/21 5:44 PM, Eli Britstein wrote:
>>> On 6/1/2021 5:35 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or
On 6/1/2021 5:53 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/1/21 5:44 PM, Eli Britstein wrote:
On 6/1/2021 5:35 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/1/21 4:24 PM, Eli Britstein wrote:
On 6
On 6/1/21 5:44 PM, Eli Britstein wrote:
>
> On 6/1/2021 5:35 PM, Andrew Rybchenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 6/1/21 4:24 PM, Eli Britstein wrote:
>>> On 6/1/2021 3:10 PM, Ilya Maximets wrote:
External email: Use caution opening links or atta
On 01/06/2021 17:44, Eli Britstein wrote:
On 6/1/2021 5:35 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/1/21 4:24 PM, Eli Britstein wrote:
On 6/1/2021 3:10 PM, Ilya Maximets wrote:
External email: Use caution opening links or attachments
On
Hi Eli,
On 01/06/2021 16:24, Eli Britstein wrote:
On 6/1/2021 3:10 PM, Ilya Maximets wrote:
External email: Use caution opening links or attachments
On 6/1/21 1:14 PM, Ivan Malov wrote:
By its very name, action PORT_ID means that packets hit an ethdev
with the
given DPDK port ID. At least t
On 6/1/2021 5:35 PM, Andrew Rybchenko wrote:
External email: Use caution opening links or attachments
On 6/1/21 4:24 PM, Eli Britstein wrote:
On 6/1/2021 3:10 PM, Ilya Maximets wrote:
External email: Use caution opening links or attachments
On 6/1/21 1:14 PM, Ivan Malov wrote:
By its ver
On 6/1/21 4:24 PM, Eli Britstein wrote:
>
> On 6/1/2021 3:10 PM, Ilya Maximets wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On 6/1/21 1:14 PM, Ivan Malov wrote:
>>> By its very name, action PORT_ID means that packets hit an ethdev
>>> with the
>>> given DPDK port ID.
Hi Ilya,
Thank you for reviewing the proposal at such short notice. I'm afraid
that prior discussions overlook the simple fact that the whole problem
is not limited to just VF representors. Action PORT_ID is also used with
respect to the admin PF's ethdev, which "represents itself" (and by no
On 6/1/2021 3:10 PM, Ilya Maximets wrote:
External email: Use caution opening links or attachments
On 6/1/21 1:14 PM, Ivan Malov wrote:
By its very name, action PORT_ID means that packets hit an ethdev with the
given DPDK port ID. At least the current comments don't state the opposite.
That
On 6/1/21 1:14 PM, Ivan Malov wrote:
> By its very name, action PORT_ID means that packets hit an ethdev with the
> given DPDK port ID. At least the current comments don't state the opposite.
> That said, since port representors had been adopted, applications like OvS
> have been misusing the actio
By its very name, action PORT_ID means that packets hit an ethdev with the
given DPDK port ID. At least the current comments don't state the opposite.
That said, since port representors had been adopted, applications like OvS
have been misusing the action. They misread its purpose as sending packet
39 matches
Mail list logo
