From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] netvsc PMD performance fixes
Date: Sun, 05 Aug 2018 11:14:06 +0200 [thread overview]
Message-ID: <1826385.DckrNDiGSl@xps> (raw)
In-Reply-To: <20180724210853.22767-1-stephen@networkplumber.org>
24/07/2018 23:08, Stephen Hemminger:
> The netvsc PMD is faster than the kernel but is still slow
> on receiving packets. These patches help.
>
> Stephen Hemminger (4):
> netvsc: change rx descriptor setup and sizing
> netvsc: avoid over filling receive descriptor ring
> netvsc: implement queue info get handles
> netvsc/vmbus: avoid signalling host on read
Applied, thanks
prev parent reply other threads:[~2018-08-05 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 21:08 Stephen Hemminger
2018-07-24 21:08 ` [dpdk-dev] [PATCH 1/4] netvsc: change rx descriptor setup and sizing Stephen Hemminger
2018-07-24 21:08 ` [dpdk-dev] [PATCH 2/4] netvsc: avoid over filling receive descriptor ring Stephen Hemminger
2018-07-24 21:08 ` [dpdk-dev] [PATCH 3/4] netvsc: implement queue info get handles Stephen Hemminger
2018-07-24 21:08 ` [dpdk-dev] [PATCH 4/4] netvsc/vmbus: avoid signalling host on read Stephen Hemminger
2018-08-05 9:14 ` Thomas Monjalon [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=1826385.DckrNDiGSl@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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 NNTP newsgroup(s).