From: David Miller <davem@davemloft.net>
To: hejianet@gmail.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
vyasevich@gmail.com, nhorman@tuxdriver.com,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
marcelo.leitner@gmail.com
Subject: Re: [PATCH v6 0/7] Reduce cache miss for snmp_fold_field
Date: Fri, 30 Sep 2016 02:14:02 -0400 (EDT) [thread overview]
Message-ID: <20160930.021402.267441690910051825.davem@davemloft.net> (raw)
In-Reply-To: <1475206144-23228-1-git-send-email-hejianet@gmail.com>
From: Jia He <hejianet@gmail.com>
Date: Fri, 30 Sep 2016 11:28:57 +0800
> In a PowerPc server with large cpu number(160), besides commit
> a3a773726c9f ("net: Optimize snmp stat aggregation by walking all
> the percpu data at once"), I watched several other snmp_fold_field
> callsites which would cause high cache miss rate.
...
Series applied, thank you.
prev parent reply other threads:[~2016-09-30 6:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 3:28 [PATCH v6 0/7] Reduce cache miss for snmp_fold_field Jia He
2016-09-30 3:28 ` [PATCH v6 1/7] net:snmp: Introduce generic interfaces for snmp_get_cpu_field{,64} Jia He
2016-09-30 3:28 ` [PATCH v6 2/7] proc: Reduce cache miss in snmp_seq_show Jia He
2016-09-30 3:29 ` [PATCH v6 3/7] proc: Reduce cache miss in snmp6_seq_show Jia He
2016-09-30 3:29 ` [PATCH v6 4/7] proc: Reduce cache miss in sctp_snmp_seq_show Jia He
2016-09-30 3:29 ` [PATCH v6 5/7] proc: Reduce cache miss in xfrm_statistics_seq_show Jia He
2016-09-30 3:29 ` [PATCH v6 6/7] ipv6: Remove useless parameter in __snmp6_fill_statsdev Jia He
2016-09-30 3:29 ` [PATCH v6 7/7] net: Suppress the "Comparison to NULL could be written" warnings Jia He
2016-09-30 6:14 ` 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=20160930.021402.267441690910051825.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hejianet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=steffen.klassert@secunet.com \
--cc=vyasevich@gmail.com \
--cc=yoshfuji@linux-ipv6.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).