From: Paolo Abeni <pabeni@redhat.com>
To: zhangliping <zhanglkk1990@163.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
zhangliping <zhangliping02@baidu.com>
Subject: Re: [PATCH net-next] udp: handle gro_receive only when necessary
Date: Mon, 18 Dec 2017 15:45:30 +0100 [thread overview]
Message-ID: <1513608330.8795.7.camel@redhat.com> (raw)
In-Reply-To: <1f4bfef5.b4c7.16069879c26.Coremail.zhanglkk1990@163.com>
On Mon, 2017-12-18 at 20:09 +0800, zhangliping wrote:
> My test case is very simple, two VMs were connected via ovs + dpdk.
> Inside VM, rps is enabled. Then one VM runs "iperf -s -u &", another
> VM runs "iperf -c 1.1.1.2 -P 12 -u -b 10Gbps -l 40 -t 36000".
Understood, thanks. Still the time spent in 'udp4_lib_lookup2' looks
quite different/higher than what I observe in my tests. Are you using
x86_64? if not, do you see many cache misses in udp4_lib_lookup2?
Thanks,
Paolo
next prev parent reply other threads:[~2017-12-18 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 4:11 [PATCH net-next] udp: handle gro_receive only when necessary zhangliping
2017-12-18 10:26 ` Paolo Abeni
2017-12-18 12:09 ` zhangliping
2017-12-18 14:45 ` Paolo Abeni [this message]
2017-12-19 11:01 ` zhangliping
2017-12-19 11:47 ` Paolo Abeni
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=1513608330.8795.7.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=zhangliping02@baidu.com \
--cc=zhanglkk1990@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.