From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>,
Tiwei Bie <tiwei.bie@intel.com>
Subject: Re: [virtio-comment] [PATCH v10] virtio-net: Clarify VLAN filter table configuration
Date: Thu, 26 Jan 2023 00:07:43 -0500 [thread overview]
Message-ID: <20230126000221-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54819A070E3D374E0BDBCEA2DCCE9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jan 25, 2023 at 11:46:58PM +0000, Parav Pandit wrote:
> > > but vlans are different aren't they? Anyway changing that will need a
> > > new feature bit.
> > I do not the history for about "Note" on why it was made best effort.
> > To best of my knowledge, it should not be best effort.
> > Device should not overflow the table. It should fail the ADD call.
For the MAC table? Failing commands generally is
a bad way to communicate to drivers. If we do there needs to also
be a way to report our limits. In this case it's enough to
look at qemu to see an implementation that just sets a "table
overflow" flag and stops filtering.
Similarly a populat vhost+bridge+tap combo does not keep
the copy of the mac table at all and instead realies on
guest sending announcement packets and bridge learning from these.
> > If the above claim of "Note" is not strong enough, we can probably run a
> > different issue to make it "MUST".
> > I am not sure we really need feature bit it we fix the note.
>
> I clicked too early while typing.
> Since DEL operation doesn't synchronize with the data path of device and driver, at some point a packet in pipe can be still received with removed VLAN.
> So may be the note was added.
> But for sure ADD should not be best effort basis.
So for VLANs this was added by Tiwei. I guess it looked sane then
but now I don't remember the motivation. Tiwei CC'd.
--
MST
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/
next prev parent reply other threads:[~2023-01-26 5:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:25 [virtio-comment] [PATCH v10] virtio-net: Clarify VLAN filter table configuration Parav Pandit
2023-01-19 18:35 ` [virtio-comment] " Parav Pandit
2023-01-25 18:04 ` [virtio-comment] " Halil Pasic
2023-01-25 19:09 ` [virtio-dev] " Parav Pandit
2023-01-25 20:31 ` [virtio-dev] " Michael S. Tsirkin
2023-01-25 20:36 ` [virtio-dev] " Parav Pandit
2023-01-26 11:48 ` Halil Pasic
2023-01-26 16:17 ` [virtio-dev] " Parav Pandit
2023-01-26 16:27 ` Michael S. Tsirkin
2023-01-25 20:55 ` Michael S. Tsirkin
2023-01-25 23:30 ` Parav Pandit
2023-01-25 23:46 ` Parav Pandit
2023-01-26 0:46 ` [virtio-dev] " Si-Wei Liu
2023-01-26 5:01 ` Michael S. Tsirkin
2023-01-26 5:07 ` Michael S. Tsirkin [this message]
2023-01-26 16:27 ` Parav Pandit
2023-01-26 16:31 ` Michael S. Tsirkin
2023-01-26 16:42 ` Parav Pandit
2023-01-26 17:15 ` Michael S. Tsirkin
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=20230126000221-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=si-wei.liu@oracle.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.