From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <ybendito@redhat.com>
Cc: Yuri Benditovich <yuri.benditovich@daynix.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v2] virtio-net: Define per-packet hash reporting feature
Date: Mon, 3 Feb 2020 08:20:56 -0500 [thread overview]
Message-ID: <20200203081229-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <926049155.4815995.1580735457487.JavaMail.zimbra@redhat.com>
On Mon, Feb 03, 2020 at 08:10:57AM -0500, Yuri Benditovich wrote:
> > > +\item The device uses \field{hash_key_data} of the virtio_net_rss_config
> > > structure.
> > > +\end{itemize}
> > > +See the definition of virtio_net_rss_config structure in \ref{sec:Device
> > > Types / Network Device / Device Operation / Control Virtqueue /
> > > Receive-side scaling (RSS) / Setting RSS parameters}
> > > +
> > > +If the feature VIRTIO_NET_F_RSS was not negotiated, the device uses
> > > internal configuration
> > > +of enabled hash types and a key used for hash calculation.
>
> > I don't understand this last paragraph. Could you clarify?
>
> In order to calculate a hash the device shall have 2 things:
> a key for hash calculation
> a bitmask which hash types are enabled
>
> In case the device supportes RSS command (even with single queue), it can take them from current RSS configuration.
> If only VIRTIO_NET_F_HASH_REPORT is negotiated, the device uses internal preset of both parameters.
>
> Do you suggest something different?
Hmm control over key/mask would be nice to have.
I guess we could add a command along the lines of:
struct virtio_net_hash_config {
le32 hash_types;
le16 reserved[4];
u8 hash_key_length;
u8 hash_key_data[hash_key_length];
};
This needs some thought: we don't want to request that devices have
double the machinery so the command should not be there if RSS is
enabled ...
Maybe the command is only valid if HASH is set but RSS is clear?
--
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:[~2020-02-03 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 10:01 [virtio-comment] [PATCH v2] virtio-net: Define per-packet hash reporting feature Yuri Benditovich
2020-02-03 10:11 ` Michael S. Tsirkin
2020-02-03 13:10 ` Yuri Benditovich
2020-02-03 13:20 ` Michael S. Tsirkin [this message]
2020-02-05 9:32 ` Yuri Benditovich
2020-02-05 10:30 ` 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=20200203081229-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=ybendito@redhat.com \
--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 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.