OASIS Virtual I/O Device (VIRTIO) TC

> From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of > Parav Pandit > Sent: Tuesday, August 1, 2023 2:04 PM > > Hi Michael and all, > > > From: Parav Pandit <parav@nvidia.com> > > Sent: Monday, July 24, 2023 9:04 AM > > > > Add virtio net device requirements for receive flow filters. > > > > Signed-off-by: Parav Pandit <parav@nvidia.com> > > Do you have any further comments on it? > > Heng and I want to progress now to start the design/spec draft of it starting 3rd > Aug. > Flow filter command requires packed VQ descriptor extension. > So, we need to wrap up now for this infrastructure extension pre-work which > has significant effort. > > For now, we are taking design to next stage for these steering requirements. > The packed vq extension is going to benefit low latency tx part as well as > reviewed by Stephan. In todays' meeting we further discussed that inline is optional feature for the txq and for steering filters. Hence, based on the feedback, we can progress now without packed vq extension. We need to close on the config space access via dma interface. So lets finish that blocker now so counters and filters can progress.

? 2023/8/2 ??2:44, Parav Pandit ??:
>
>> From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of
>> Parav Pandit
>> Sent: Tuesday, August 1, 2023 2:04 PM
>>
>> Hi Michael and all,
>>
>>> From: Parav Pandit <parav@nvidia.com>
>>> Sent: Monday, July 24, 2023 9:04 AM
>>>
>>> Add virtio net device requirements for receive flow filters.
>>>
>>> Signed-off-by: Parav Pandit <parav@nvidia.com>
>> Do you have any further comments on it?
>>
>> Heng and I want to progress now to start the design/spec draft of it starting 3rd
>> Aug.
>> Flow filter command requires packed VQ descriptor extension.
>> So, we need to wrap up now for this infrastructure extension pre-work which
>> has significant effort.
>>
>> For now, we are taking design to next stage for these steering requirements.
>> The packed vq extension is going to benefit low latency tx part as well as
>> reviewed by Stephan.
> In todays' meeting we further discussed that inline is optional feature for the txq and for steering filters.
> Hence, based on the feedback, we can progress now without packed vq extension.

Hi, Parav.
I remember that the last meeting (7.26) was canceled and the meeting was
postponed until today (8.02)?
If yes, unfortunately we missed this meeting :(.

Is the next meeting still two weeks away (8.16) ?

Thanks!

>
> We need to close on the config space access via dma interface.
> So lets finish that blocker now so counters and filters can progress.
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/

å 2023/8/2 äå2:44, Parav Pandit åé: From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of Parav Pandit Sent: Tuesday, August 1, 2023 2:04 PM Hi Michael and all, From: Parav Pandit <parav@nvidia.com> Sent: Monday, July 24, 2023 9:04 AM Add virtio net device requirements for receive flow filters. Signed-off-by: Parav Pandit <parav@nvidia.com> Do you have any further comments on it? Heng and I want to progress now to start the design/spec draft of it starting 3rd Aug. Flow filter command requires packed VQ descriptor extension. So, we need to wrap up now for this infrastructure extension pre-work which has significant effort. For now, we are taking design to next stage for these steering requirements. The packed vq extension is going to benefit low latency tx part as well as reviewed by Stephan. In todays' meeting we further discussed that inline is optional feature for the txq and for steering filters. Hence, based on the feedback, we can progress now without packed vq extension. Hi, Parav. I remember that the last meeting (7.26) was canceled and the meeting was postponed until today (8.02)? If yes, unfortunately we missed this meeting :(. Is the next meeting still two weeks away (8.16) ? Thanks! We need to close on the config space access via dma interface. So lets finish that blocker now so counters and filters can progress. This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/

> From: Heng Qi <hengqi@linux.alibaba.com>
> Sent: Wednesday, August 2, 2023 9:03 PM

> Hi, Parav.
> I remember that the last meeting (7.26) was canceled and the meeting was
> postponed until today (8.02)?
> If yes, unfortunately we missed this meeting :(.
>
> Is the next meeting still two weeks away (8.16) ?
>
Yes. I was severely ill during last two weeks, so cancelled it.
I am sorry for the disruption.
We will continue the regular schedule of 8/16.

> From: Heng Qi <hengqi@linux.alibaba.com> > Sent: Wednesday, August 2, 2023 9:03 PM > Hi, Parav. > I remember that the last meeting (7.26) was canceled and the meeting was > postponed until today (8.02)? > If yes, unfortunately we missed this meeting :(. > > Is the next meeting still two weeks away (8.16) ? > Yes. I was severely ill during last two weeks, so cancelled it. I am sorry for the disruption. We will continue the regular schedule of 8/16.

? 2023/8/3 ??6:01, Parav Pandit ??:
>> From: Heng Qi <hengqi@linux.alibaba.com>
>> Sent: Wednesday, August 2, 2023 9:03 PM
>> Hi, Parav.
>> I remember that the last meeting (7.26) was canceled and the meeting was
>> postponed until today (8.02)?
>> If yes, unfortunately we missed this meeting :(.
>>
>> Is the next meeting still two weeks away (8.16) ?
>>
> Yes. I was severely ill during last two weeks, so cancelled it.

I'm sorry to hear that. Please take good care!

> I am sorry for the disruption.
> We will continue the regular schedule of 8/16.

Ok, we'll be friendly on time!

Thanks.

å 2023/8/3 äå6:01, Parav Pandit åé: From: Heng Qi <hengqi@linux.alibaba.com> Sent: Wednesday, August 2, 2023 9:03 PM Hi, Parav. I remember that the last meeting (7.26) was canceled and the meeting was postponed until today (8.02)? If yes, unfortunately we missed this meeting :(. Is the next meeting still two weeks away (8.16) ? Yes. I was severely ill during last two weeks, so cancelled it. I'm sorry to hear that. Please take good care! I am sorry for the disruption. We will continue the regular schedule of 8/16. Ok, we'll be friendly on time! Thanks.