[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: virtio-net collaboration bi-weekly
Hi All, Sorry for the delayed summary. Meeting summary: 6/21/23: Design discussion on receive flow filters. 1. Should have ability to create one or more queues to carry flow filter commands 2. Separate q from control vq has ability gradually implement ops from sw to hw or semi hw a. Contains very different commands than cvq commands. 3. Mac and vlan filter commands are first priority filters. a. They do not as optimize as newly proposed commands which cover wider use cases. 4. Ability to destroy or invalidate the full filter table is needed 5. Ability to batch is good to have, but not must in first phase (ARFS timer flow may find it useful) 6. No good use case for rule modification, so will be dropped. Only add, delete, and modify. Add can implicitly modify the existing rules if use case arises. 7. CVQ is not good fit for high rate flow commands. 8. Spec to document the flow filters priority with existing mac, vlan filters. 9. Should have the ability to add/delete the flow queues when feature is enabled/disabled later in the driver life cycle. Open questions: 1. Should flow vq disable should delete the rules if when multiple queues are active? My take is: it should not. A device reset of explicit flow table destroy should delete the filter rules. 2. Should we define a generic VQ to have flow specific command class, and command opcode, so that we donât have to create too many queue types? Next steps: 1. Update details to v2 and sign off the requirements to start with interface, command definition. 2. Finalize above open questions and any other open items. Agenda for 6th July: 1. Close on any open items for above requirements. -----Original Appointment----- From: parav@nvidia.com <parav@nvidia.com> Sent: Friday, June 2, 2023 11:00 AM To: parav@nvidia.com; pandit.parav@gmail.com; hengqi@linux.alibaba.com; sburla@marvell.com; si-wei.liu@oracle.com; virtio-comment@lists.oasis-open.org; virtio@lists.oasis-open.org; xuanzhuo@linux.alibaba.com Subject: virtio-net collaboration bi-weekly When: Wednesday, June 21, 2023 5:00 AM-5:45 AM tzone://Microsoft/Utc. Where: virtio-net collaboration bi-weekly Join with Google Meet â Hi All,This is a bi-weekly collaboration meeting for virtio net specification developers.This week agenda:1. Discuss virtio net 1.4 feature requirements posted at [1] and any others.https://lists.oasi  https://meet.google.com/gkj-rawi-ufp?hs=224 Meeting link https://meet.google.com/gkj-rawi-ufp?hs=224 Join by phone (US) tel:+1-978-403-0584%3B756969764%23 PIN: 756969764 https://tel.meet/gkj-rawi-ufp?pin=7573680783326&hs=0 Hi All, This is a bi-weekly collaboration meeting for virtio net specification developers. This week agenda: 1. Discuss virtio net 1.4 feature requirements posted at [1] and any others. https://www.google.com/url?q=https%3A%2F%2Flists.oasis-open.org%2Farchives%2Fvirtio-comment%2F202306%2Fmsg00015.html&sa=D&ust=1686149940000000&usg=AOvVaw0hp2bsXL4FfP_iO-EL4yWl  2. inner hash open  ------- a. All decisions are still made by TC electronic ballot asusual. Proposed collaboration meetingsare unrelated to TC ballot. b. All discussions follow OASIS feedback license. https://www.google.com/url?q=https%3A%2F%2Fwww.oasis-open.org%2Fpolicies-guidelines%2Fipr%2F%23appendixa&sa=D&ust=1686149940000000&usg=AOvVaw2C-QOcWPhEQShtnNHuu4c1 When Every 2 weeks from 12am to 12:45am on Wednesday (Central Time - Chicago) Guests mailto:parav@nvidia.com - organizer mailto:pandit.parav@gmail.com mailto:hengqi@linux.alibaba.com mailto:sburla@marvell.com mailto:si-wei.liu@oracle.com mailto:virtio-comment@lists.oasis-open.org mailto:virtio@lists.oasis-open.org mailto:xuanzhuo@linux.alibaba.com https://calendar.google.com/calendar/event?action=VIEW&eid=N3I1MWdiNjBsanY1MTJwN2dudDF0ZmJuaWYgdmlydGlvLWNvbW1lbnRAbGlzdHMub2FzaXMtb3Blbi5vcmc&tok=MTYjcGFyYXZAbnZpZGlhLmNvbWRmYTBiMzkzNzMyOTIzZjg0MmUxMzhlYjFhNDVhNDgyNmI4YThkZjk&ctz=America%2FChicago&hl=en&es=0 RSVP for mailto:virtio-comment@lists.oasis-open.org for all events in this series https://calendar.google.com/calendar/event?action=RESPOND&eid=N3I1MWdiNjBsanY1MTJwN2dudDF0ZmJuaWYgdmlydGlvLWNvbW1lbnRAbGlzdHMub2FzaXMtb3Blbi5vcmc&rst=1&tok=MTYjcGFyYXZAbnZpZGlhLmNvbWRmYTBiMzkzNzMyOTIzZjg0MmUxMzhlYjFhNDVhNDgyNmI4YThkZjk&ctz=America%2FChicago&hl=en&es=0 https://calendar.google.com/calendar/event?action=RESPOND&eid=N3I1MWdiNjBsanY1MTJwN2dudDF0ZmJuaWYgdmlydGlvLWNvbW1lbnRAbGlzdHMub2FzaXMtb3Blbi5vcmc&rst=2&tok=MTYjcGFyYXZAbnZpZGlhLmNvbWRmYTBiMzkzNzMyOTIzZjg0MmUxMzhlYjFhNDVhNDgyNmI4YThkZjk&ctz=America%2FChicago&hl=en&es=0 https://calendar.google.com/calendar/event?action=RESPOND&eid=N3I1MWdiNjBsanY1MTJwN2dudDF0ZmJuaWYgdmlydGlvLWNvbW1lbnRAbGlzdHMub2FzaXMtb3Blbi5vcmc&rst=3&tok=MTYjcGFyYXZAbnZpZGlhLmNvbWRmYTBiMzkzNzMyOTIzZjg0MmUxMzhlYjFhNDVhNDgyNmI4YThkZjk&ctz=America%2FChicago&hl=en&es=0 https://calendar.google.com/calendar/event?action=VIEW&eid=N3I1MWdiNjBsanY1MTJwN2dudDF0ZmJuaWYgdmlydGlvLWNvbW1lbnRAbGlzdHMub2FzaXMtb3Blbi5vcmc&tok=MTYjcGFyYXZAbnZpZGlhLmNvbWRmYTBiMzkzNzMyOTIzZjg0MmUxMzhlYjFhNDVhNDgyNmI4YThkZjk&ctz=America%2FChicago&hl=en&es=0 Invitation from https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. https://support.google.com/calendar/answer/37135#forwarding
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]