From: Rick Jones <rick.jones2@hpe.com>
To: Eric Dumazet <eric.dumazet@gmail.com>, Tom Herbert <tom@herbertland.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH v2 net-next 4/5] xps_flows: XPS for packets that don't have a socket
Date: Thu, 29 Sep 2016 09:35:25 -0700 [thread overview]
Message-ID: <582e5e4e-ec5e-aafc-218d-7e7411ecc45b@hpe.com> (raw)
In-Reply-To: <1475155080.28155.159.camel@edumazet-glaptop3.roam.corp.google.com>
On 09/29/2016 06:18 AM, Eric Dumazet wrote:
> Well, then what this patch series is solving ?
>
> You have a producer of packets running on 8 vcpus in a VM.
>
> Packets are exiting the VM and need to be queued on a mq NIC in the
> hypervisor.
>
> Flow X can be scheduled on any of these 8 vcpus, so XPS is currently
> selecting different TXQ.
Just for completeness, in my testing, the VMs were single-vCPU.
rick jones
next prev parent reply other threads:[~2016-09-29 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 3:54 [PATCH v2 net-next 0/5] xps_flows: XPS flow steering when there is no socket Tom Herbert
2016-09-29 3:54 ` [PATCH v2 net-next 1/5] net: Set SW hash in skb_set_hash_from_sk Tom Herbert
2016-09-29 3:54 ` [PATCH v2 net-next 2/5] dql: Add counters for number of queuing and completion operations Tom Herbert
2016-09-29 3:54 ` [PATCH v2 net-next 3/5] net: Add xps_dev_flow_table_cnt Tom Herbert
2016-09-29 3:54 ` [PATCH v2 net-next 4/5] xps_flows: XPS for packets that don't have a socket Tom Herbert
2016-09-29 4:54 ` Eric Dumazet
2016-09-29 12:53 ` Tom Herbert
2016-09-29 13:18 ` Eric Dumazet
2016-09-29 14:08 ` Tom Herbert
2016-09-29 14:51 ` Eric Dumazet
2016-09-29 15:15 ` Eric Dumazet
2016-09-29 20:26 ` Tom Herbert
2016-09-29 16:35 ` Rick Jones [this message]
2016-09-29 3:54 ` [PATCH v2 net-next 5/5] xps: Documentation for transmit socketles flow steering Tom Herbert
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=582e5e4e-ec5e-aafc-218d-7e7411ecc45b@hpe.com \
--to=rick.jones2@hpe.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).