From: Parav Pandit <parav@nvidia.com>
To: Parav Pandit <parav@nvidia.com>,
"hengqi@linux.alibaba.com" <hengqi@linux.alibaba.com>,
"sburla@marvell.com" <sburla@marvell.com>,
"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"dust.li@linux.alibaba.com" <dust.li@linux.alibaba.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: [virtio-comment] RE: virtio-net collaboration bi-weekly
Date: Wed, 7 Jun 2023 06:08:52 +0000 [thread overview]
Message-ID: <PH0PR12MB5481C2BB67360737A57FA270DC53A@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH0PR12MB5481DBEAA12D6B22289D99E6DC4EA@PH0PR12MB5481.namprd12.prod.outlook.com>
Minutes: 6/7/2023
1.4 features:
1. Parav introduced features at high level (3 are perf improvements and 3 are new functionality) of 1.4.
2. Team discussed eswitch model for SR-IOV in context of ntuple flow steering.
a. David explained the use cases of host where hypervisor managed the full nic, can find group owner to have the PF.
b. Si-Wei explained the useful ness of ip link vf, however it is is deprecated model in Linux for VF management, hence basic tc flower can be done.
3. Participants virtio net hw device vendors and users have VF eswitch on separate host (not on the group owner PF).
Hence, no pressing need to bring eswitch steering in 1.4-time frame.
a. A very basic packet forwarding among VFs could be useful in future.
b. N-tuple steering model to have concept of network port so that when future switch arrives, it can get the building block.
4. David requested to have the mtu configuration to device is useful.
MTU configuration by the driver is missing. It is useful for driver to indicate it to the device.
a. This helps physical device to manage buffer efficiently.
b. This also helps device to drop large packets which driver should not receive.
5. Inner hash review is pending/slowed down for a while in v14 (Parav); should finish the review sooner.
Next meeting 6/21 agenda:
1. Discuss any open items for 1.4 requirements v0 and v1 posted/will be posted on mailing list
-----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 7, 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
next parent reply other threads:[~2023-06-07 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR12MB5481DBEAA12D6B22289D99E6DC4EA@PH0PR12MB5481.namprd12.prod.outlook.com>
2023-06-07 6:08 ` Parav Pandit [this message]
2023-06-26 3:04 ` [virtio-comment] RE: virtio-net collaboration bi-weekly Parav Pandit
2023-07-16 20:00 ` Parav Pandit
2023-11-08 6:36 ` Parav Pandit
2023-11-22 10:19 ` Parav Pandit
2024-01-10 3:45 [virtio-comment] " Parav Pandit
2024-01-10 3:55 ` [virtio-comment] " Xuan Zhuo
2024-01-10 4:42 ` [virtio-comment] " Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR12MB5481C2BB67360737A57FA270DC53A@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=dust.li@linux.alibaba.com \
--cc=hengqi@linux.alibaba.com \
--cc=jiri@nvidia.com \
--cc=sburla@marvell.com \
--cc=si-wei.liu@oracle.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).