From: Jeff Garzik <jgarzik@pobox.com>
To: akpm@osdl.org
Cc: davem@davemloft.net, netdev@oss.sgi.com, christoph@graphe.net,
nirajk@calsoftinc.com, christoph@lameter.com, Shai@Scalex86.org
Subject: Re: [patch 05/13] remove last_rx update from loopback device
Date: Tue, 15 Mar 2005 17:41:39 -0500 [thread overview]
Message-ID: <423764A3.8030201@pobox.com> (raw)
In-Reply-To: <200503152222.j2FMMbhG016805@shell0.pdx.osdl.net>
akpm@osdl.org wrote:
> From: Christoph Lameter <christoph@graphe.net>
>
> The last_rx field in the loopback driver is updated on every xmit but is
> not used otherwise. Accesses to ->last_rx cause unecessary traffic on the
> interlink for NUMA systems which limits the performance of the loopback
> device.
>
> The comment given at include/linux/netdevice.h says that last_rx may be
> used for future network-power-down code, which is likely not relevant for
> the loopback device (please let me know if it is otherwise ..).
>
> Signed-off-by: Niraj Kumar <nirajk@calsoftinc.com>
> Signed-off-by: Christoph Lameter <christoph@lameter.com>
> Signed-off-by: Shai Fultheim <Shai@Scalex86.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> 25-akpm/drivers/net/loopback.c | 2 --
> 1 files changed, 2 deletions(-)
>
> diff -puN drivers/net/loopback.c~remove-last_rx-update-from-loopback-device drivers/net/loopback.c
> --- 25/drivers/net/loopback.c~remove-last_rx-update-from-loopback-device Tue Mar 15 14:19:53 2005
> +++ 25-akpm/drivers/net/loopback.c Tue Mar 15 14:19:53 2005
> @@ -144,8 +144,6 @@ static int loopback_xmit(struct sk_buff
> return 0;
> }
>
> - dev->last_rx = jiffies;
> -
> lb_stats = &per_cpu(loopback_stats, get_cpu());
> lb_stats->rx_bytes += skb->len;
> lb_stats->tx_bytes += skb->len;
I disagree. loopback.c is doing precisely what it should be doing.
Jeff
next prev parent reply other threads:[~2005-03-15 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 22:22 [patch 05/13] remove last_rx update from loopback device akpm
2005-03-15 22:41 ` Jeff Garzik [this message]
2005-03-15 23:08 ` Andrew Morton
2005-03-16 0:53 ` David S. Miller
2005-03-16 1:04 ` Rick Jones
2005-03-16 1:17 ` David S. Miller
2005-03-16 1:23 ` Nivedita Singhvi
2005-03-16 1:49 ` Rick Jones
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=423764A3.8030201@pobox.com \
--to=jgarzik@pobox.com \
--cc=Shai@Scalex86.org \
--cc=akpm@osdl.org \
--cc=christoph@graphe.net \
--cc=christoph@lameter.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=nirajk@calsoftinc.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).