From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH net-next 1/2] macvtap: avoid hash calculating for single queue
Date: Fri, 15 Jul 2016 14:40:54 -0700 (PDT) [thread overview]
Message-ID: <20160715.144054.1758876801096882335.davem@davemloft.net> (raw)
In-Reply-To: <1468568791-30024-1-git-send-email-jasowang@redhat.com>
From: Jason Wang <jasowang@redhat.com>
Date: Fri, 15 Jul 2016 03:46:30 -0400
> We decide the rxq through calculating its hash which is not necessary
> if we only have one rx queue. So this patch skip this and just return
> queue 0. Test shows 22% improving on guest rx pps.
>
> Before: 1201504 pkts/s
> After: 1472731 pkts/s
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Applied.
prev parent reply other threads:[~2016-07-15 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 7:46 [PATCH net-next 1/2] macvtap: avoid hash calculating for single queue Jason Wang
2016-07-15 7:46 ` [PATCH net-next 2/2] macvtap: switch to use skb array Jason Wang
2016-07-15 21:41 ` David Miller
2016-07-15 21:40 ` David Miller [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=20160715.144054.1758876801096882335.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).