netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: edumazet@google.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
	yoshfuji@linux-ipv6.org, kaber@trash.net, jiri@resnulli.us,
	hannes@stressinduktion.org, tom@herbertland.com,
	azhou@nicira.com, ebiederm@xmission.com, ipm@chirality.org.uk,
	nicolas.dichtel@6wind.com, serge.hallyn@canonical.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	anton@au1.ibm.com, nacc@linux.vnet.ibm.com,
	srikar@linux.vnet.ibm.com
Subject: Re: [PATCH RFC V2 2/2] net: Optimize snmp stat aggregation by walking all the percpu data at once
Date: Sat, 29 Aug 2015 13:23:13 +0530	[thread overview]
Message-ID: <55E164E9.4060700@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150828.221151.233357371571169851.davem@davemloft.net>

On 08/29/2015 10:41 AM, David Miller wrote:
> From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
> Date: Sat, 29 Aug 2015 08:27:15 +0530
>
>> resending the patch with memset. Please let me know if you want to
>> resend all the patches.
>
> Do not post patches as replies to existing discussion threads.
>
> Instead, make a new, fresh, patch posting, updating the Subject line
> as needed.
>

Sure.

      reply	other threads:[~2015-08-29  7:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 17:37 [PATCH RFC V2 0/2] Optimize the snmp stat aggregation for large cpus Raghavendra K T
2015-08-26 17:37 ` [PATCH RFC V2 1/2] net: Introduce helper functions to get the per cpu data Raghavendra K T
2015-08-26 17:37 ` [PATCH RFC V2 2/2] net: Optimize snmp stat aggregation by walking all the percpu data at once Raghavendra K T
2015-08-27 18:38   ` David Miller
2015-08-28  6:39     ` Raghavendra K T
2015-08-28 18:24       ` David Miller
2015-08-28 19:20         ` Joe Perches
2015-08-28 20:33           ` Eric Dumazet
2015-08-28 20:53             ` Joe Perches
2015-08-28 20:55               ` Eric Dumazet
2015-08-28 21:09                 ` Joe Perches
2015-08-28 21:14                   ` Eric Dumazet
2015-08-28 21:26                     ` Joe Perches
2015-08-28 22:29                       ` Eric Dumazet
2015-08-28 23:12                         ` Joe Perches
2015-08-29  0:06                           ` Eric Dumazet
2015-08-29  0:35                             ` Joe Perches
2015-08-29  0:59                               ` Eric Dumazet
2015-08-29  2:57         ` Raghavendra K T
2015-08-29  3:26           ` Eric Dumazet
2015-08-29  7:52             ` Raghavendra K T
2015-08-29  5:11           ` David Miller
2015-08-29  7:53             ` Raghavendra K T [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=55E164E9.4060700@linux.vnet.ibm.com \
    --to=raghavendra.kt@linux.vnet.ibm.com \
    --cc=anton@au1.ibm.com \
    --cc=azhou@nicira.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=edumazet@google.com \
    --cc=hannes@stressinduktion.org \
    --cc=ipm@chirality.org.uk \
    --cc=jiri@resnulli.us \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nacc@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=serge.hallyn@canonical.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=tom@herbertland.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).