From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: dada1@cosmosbay.com, netdev@vger.kernel.org
Subject: Re: [RFC,PATCH] loopback: calls netif_receive_skb() instead of netif_rx()
Date: Mon, 3 Mar 2008 21:15:35 -0800 [thread overview]
Message-ID: <20080303211535.03e3c81e@extreme> (raw)
In-Reply-To: <20080303.205558.114610030.davem@davemloft.net>
On Mon, 03 Mar 2008 20:55:58 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Eric Dumazet <dada1@cosmosbay.com>
> Date: Sat, 01 Mar 2008 11:26:17 +0100
>
> > You are absolutly right. We should guard against recursion, using a new field
> > in "pcpu_lstats" (cheap access in a hot cache line as we have to update stats
> > anyway)
> ...
> > [PATCH] loopback: calls netif_receive_skb() instead of netif_rx()
>
> I'm willing to seriously entertain this change and stick it
> into net-2.6.26 if you will perform a reasonable deep stack
> test.
>
> For example, create an XFS filesystem, and mount it NFS over
> loopback. Then stress it like crazy.
>
> See if this generates stack overflows or weird crashes.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Also (unrealistic) benchmarks often test loopback performance, so you
should also check for performance gains/losses in things like
netbench, netperf, tbench, etc.
next prev parent reply other threads:[~2008-03-04 5:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:51 [RFC,PATCH] loopback: calls netif_receive_skb() instead of netif_rx() Eric Dumazet
2008-02-21 20:14 ` Daniel Lezcano
2008-02-21 23:19 ` Eric Dumazet
2008-02-22 10:19 ` Daniel Lezcano
2008-02-27 2:21 ` David Miller
2008-02-27 7:20 ` Jarek Poplawski
2008-02-27 7:23 ` David Miller
2008-02-27 7:34 ` Jarek Poplawski
2008-03-01 10:26 ` Eric Dumazet
2008-03-04 4:55 ` David Miller
2008-03-04 5:15 ` Stephen Hemminger [this message]
2008-03-04 6:27 ` Eric Dumazet
2008-03-23 10:29 ` David Miller
2008-03-23 18:48 ` Eric Dumazet
2008-03-23 19:15 ` Andi Kleen
2008-03-29 1:36 ` David Miller
2008-03-29 8:18 ` Eric Dumazet
2008-03-29 23:54 ` David Miller
2008-03-31 6:38 ` Eric Dumazet
2008-03-31 9:48 ` Ingo Molnar
2008-03-31 10:01 ` Eric Dumazet
2008-03-31 10:12 ` Ingo Molnar
2008-04-01 9:19 ` Eric Dumazet
2008-04-03 14:06 ` Pavel Machek
2008-04-03 16:19 ` Eric Dumazet
2008-03-31 10:08 ` David Miller
2008-03-31 10:44 ` Ingo Molnar
2008-03-31 11:02 ` David Miller
2008-03-31 11:36 ` poor network loopback performance and scalability (was: Re: [RFC,PATCH] loopback: calls netif_receive_skb() instead of netif_rx()) Ingo Molnar
2008-04-21 3:24 ` Herbert Xu
2008-04-21 3:38 ` poor network loopback performance and scalability David Miller
2008-04-21 8:11 ` Ingo Molnar
2008-04-21 8:16 ` David Miller
2008-04-21 10:19 ` Herbert Xu
2008-04-21 10:22 ` David Miller
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=20080303211535.03e3c81e@extreme \
--to=shemminger@vyatta.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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.