From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Jochen Behrens <jbehrens@vmware.com>, yongwang@vmware.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/vmxnet3: add interrupt support in MSI-X
Date: Tue, 13 Jul 2021 12:31:52 +0300 [thread overview]
Message-ID: <e6d82003-e276-7326-de1d-d4fd2880f7ea@oktetlabs.ru> (raw)
In-Reply-To: <20210708140225.583-1-jbehrens@vmware.com>
On 7/8/21 5:02 PM, Jochen Behrens wrote:
> Add support for MSI-X interrupt vectors to the vmxnet3 driver.
> This will allow more efficient deployments in cloud environments.
>
> By default it will try to allocate 1 vector (0) for link
> event and one MSI-X vector for each Rx queue. To simplify
> things, it will only be enabled if the number of Tx and Rx
> queues are equal (so that Tx/Rx share the same vector).
> If for any reason vmxnet3 cannot enable intr mode, it will
> fall back to the LSC only mode.
>
> v2: addressed formatting nits in comments
>
> Signed-off-by: Yong Wang <yongwang@vmware.com>
> Signed-off-by: Jochen Behrens <jbehrens@vmware.com>
Applied, thanks.
prev parent reply other threads:[~2021-07-13 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:02 Jochen Behrens
2021-07-13 9:31 ` Andrew Rybchenko [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=e6d82003-e276-7326-de1d-d4fd2880f7ea@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.com \
--cc=yongwang@vmware.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;
as well as URLs for NNTP newsgroup(s).