From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "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>
Subject: [virtio-comment] Re: [PATCH v4] virtio-network: Clarify VLAN filter table configuration
Date: Wed, 4 Jan 2023 08:38:03 -0500 [thread overview]
Message-ID: <20230104083633-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481AC6618719A63E6801190DCF59@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jan 04, 2023 at 01:28:55PM +0000, Parav Pandit wrote:
>
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, January 4, 2023 1:41 AM
> >
> > On Wed, Jan 04, 2023 at 06:02:05AM +0200, Parav Pandit wrote:
> > > The filtering behavior of the VLAN filter commands is not very clear
> > > as discussed in thread [1].
> > >
> > > Hence, add the command description and device requirements for it.
> > >
> > > [1] https://www.mail-archive.com/qemu-devel@nongnu.org/msg912392.html
> > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/147
> > > Suggested-by: Si-Wei Liu <si-wei.liu@oracle.com>
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> >
> > Looks like we are going back to issues that we had in v1.
> > what happened here?
> >
> I was missing text in v3 for the case of device behavior for handling vlan tagged packets when CTRL_VLAN is not negotiated.
> Which I added in v4. Parts of the v1 was taken care. More below.
> [..]
> > > +
> > > +VIRTIO_NET_CTRL_VLAN_DEL command removes specified VLAN from the
> > VLAN
> >
> > the specified
> >
> Ack.
>
> > > +filtering table which was previously added using
> > > +VIRTIO_NET_CTRL_VLAN_ADD command.
> >
> > bad ordering so it's unclear what was added. it's vlan not the table. So:
> > removes the specified VLAN - which was previously added using
> > VIRTIO_NET_CTRL_VLAN_ADD command - from the VLAN filtering
> > table.
> >
> Ack.
>
> > > +
> > > +\devicenormative{\subparagraph}{VLAN Filtering}{Device Types /
> > > +Network Device / Device Operation / Control Virtqueue / VLAN
> > > +Filtering}
> > > +
> > > +When VIRTIO_NET_F_CTRL_VLAN is not negotiated, the device accepts all
> > > +VLAN tagged packets that matches the device's filter configuration.
> >
> > bad grammar here and it's not a match.
> >
> How about,
>
> When VIRTIO_NET_F_CTRL_VLAN is not negotiated, the device accepts
> all VLAN tagged packets based on the device configuration.
We came up with a better wording e.g. in
20230103054736-mutt-send-email-mst@kernel.org .
> Above spec line covers
> (a) existing mac filter table entries
> (b) promiscuous variations and
> (c) future filtering rules.
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-04 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 4:02 [virtio-comment] [PATCH v4] virtio-network: Clarify VLAN filter table configuration Parav Pandit
2023-01-04 6:41 ` [virtio-comment] " Michael S. Tsirkin
2023-01-04 13:28 ` [virtio-comment] " Parav Pandit
2023-01-04 13:38 ` Michael S. Tsirkin [this message]
2023-01-06 18:22 ` 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=20230104083633-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=si-wei.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox