Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] Re: [PATCH v5 0/1] Define VIRTIO_NET_F_HASH_REPORT feature
Date: Thu, 27 Feb 2020 04:57:47 -0500	[thread overview]
Message-ID: <20200227045632-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOEp5Od3h1RXQxFNW4bnugK1BVS26CxM+zHsAUo7GsZpAvXJrQ@mail.gmail.com>

On Thu, Feb 27, 2020 at 11:49:50AM +0200, Yuri Benditovich wrote:
> If seems OK, please initiate the ballot

Sure. Please update the main description - it seems to be incomplete -
and include the final proposal link the in the main description -
it's in the comments now. Then let me know.

> On Thu, Feb 20, 2020 at 8:47 AM Yuri Benditovich
> <yuri.benditovich@daynix.com> wrote:
> >
> > Changes from v4:
> > Added padding_reserved field to the packet layout
> > Renamed hash_type field in the packet layout to hash_report
> >
> > Changes from v3:
> > Rebased to latest master branch
> > Changes feature number to 57 (as 58 is under discussion)
> > Minor changes according to v3 review
> >
> > Yuri Benditovich (1):
> >   virtio-net: Define per-packet hash reporting feature
> >
> >  content.tex | 348 ++++++++++++++++++++++++++++++++++------------------
> >  1 file changed, 230 insertions(+), 118 deletions(-)
> >
> > --
> > 2.17.1
> >


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/


      reply	other threads:[~2020-02-27  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  6:46 [virtio-comment] [PATCH v5 0/1] Define VIRTIO_NET_F_HASH_REPORT feature Yuri Benditovich
2020-02-20  6:46 ` [virtio-comment] [PATCH v5 1/1] virtio-net: Define per-packet hash reporting feature Yuri Benditovich
2020-02-27  9:49 ` [virtio-comment] Re: [PATCH v5 0/1] Define VIRTIO_NET_F_HASH_REPORT feature Yuri Benditovich
2020-02-27  9:57   ` Michael S. Tsirkin [this message]

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=20200227045632-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=yuri.benditovich@daynix.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