From: Jisheng Zhang <jszhang@marvell.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Dmitry Popov <ixaphire@qrator.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Weird NET_RX softirq behavior
Date: Fri, 8 Aug 2014 14:55:33 +0800 [thread overview]
Message-ID: <20140808145533.5675e695@xhacker> (raw)
In-Reply-To: <1407476878.3604.0.camel@edumazet-glaptop2.roam.corp.google.com>
On Thu, 7 Aug 2014 22:47:58 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Fri, 2014-08-08 at 10:37 +0800, Jisheng Zhang wrote:
> > nd and recive 7 packets so far, about 1400bytes. Seems small
> > comparing with the CPU1 and CPU2 NET_RX softirq numbers, right?
> >
> > Any other possible case?
>
> Multicast loop. Check dev_loopback_xmit() and its callers.
>
>
That's it! This make sense
I didn't see any NET_RX on CPU1,2,3 if I disabled mulitcast
Thanks very much.
prev parent reply other threads:[~2014-08-08 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 9:10 Weird NET_RX softirq behavior Jisheng Zhang
2014-08-07 14:18 ` Dmitry Popov
2014-08-08 2:37 ` Jisheng Zhang
2014-08-08 5:47 ` Eric Dumazet
2014-08-08 6:55 ` Jisheng Zhang [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=20140808145533.5675e695@xhacker \
--to=jszhang@marvell.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ixaphire@qrator.net \
--cc=linux-kernel@vger.kernel.org \
--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 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).