From: Parav Pandit <parav@nvidia.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] RE: [PATCH v2 7/7] virtio-net: Describe RSS using receive queue handle
Date: Tue, 21 Mar 2023 21:15:00 +0000 [thread overview]
Message-ID: <PH0PR12MB548122E08C57CFF8C793BC61DC819@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH0PR12MB548130EED53ADA3C384E5A1DDC819@PH0PR12MB5481.namprd12.prod.outlook.com>
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Parav Pandit
> But I guess we can describe by duplicating the text and avoiding rq_handle as
> you suggest.
> Will simplify this in v3.
Looking further, we refer to rq_handle in more than 2 places, at indirection_table_mask field too.
So I am keeping it, moving it ahead so that all 3 places can refer it.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-03-21 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 4:10 [virtio-dev] [PATCH v2 0/7] Rename queue index to queue number Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 1/7] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-21 9:01 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-03-21 20:43 ` [virtio-dev] " Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 2/7] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 3/7] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 4/7] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 5/7] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-21 8:46 ` [virtio-dev] " Michael S. Tsirkin
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 6/7] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 7/7] virtio-net: Describe RSS using receive queue handle Parav Pandit
2023-03-21 8:55 ` [virtio-dev] " Michael S. Tsirkin
2023-03-21 20:54 ` [virtio-dev] " Parav Pandit
2023-03-21 21:15 ` Parav Pandit [this message]
2023-03-21 9:05 ` [virtio-dev] Re: [PATCH v2 0/7] Rename queue index to queue number Michael S. Tsirkin
2023-03-21 20:57 ` [virtio-dev] " 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=PH0PR12MB548122E08C57CFF8C793BC61DC819@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=shahafs@nvidia.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).