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: Tue, 19 Dec 2017 12:47:29 +0100 [thread overview]
Message-ID: <1513684049.2656.12.camel@redhat.com> (raw)
In-Reply-To: <581a1e57.7029.1606e6f4d4f.Coremail.zhanglkk1990@163.com>
On Tue, 2017-12-19 at 19:01 +0800, zhangliping wrote:
> At 2017-12-18 22:45:30, "Paolo Abeni" <pabeni@redhat.com> wrote:
> > 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?
>
> Yes, x86_64. Here is the host's lscpu output info:
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 12
> On-line CPU(s) list: 0-11
> Thread(s) per core: 1
> Core(s) per socket: 6
> CPU socket(s): 2
> NUMA node(s): 2
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 62
> Stepping: 4
> CPU MHz: 2095.074
> BogoMIPS: 4196.28
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 15360K
> NUMA node0 CPU(s): 0-5
> NUMA node1 CPU(s): 6-11
>
> Btw, my guest OS is Centos 3.10.0-514.26.2.el7.x86_64, is this kernel
> too old to be tested?
Understood. Yes, such kernel is a bit too old. So the perf trace you
reported refer to the CentOS kernel?
If you try a current vanilla kernel (or an upcoming rhel 7.5, for
shameless self promotion) you should see much better figures (and a
smaller differenct with your patch in)
Cheers,
Paolo
prev parent reply other threads:[~2017-12-19 11:47 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
2017-12-19 11:01 ` zhangliping
2017-12-19 11:47 ` Paolo Abeni [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=1513684049.2656.12.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.