From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shawn Bohrer <sbohrer@rgmadvisors.com>
Cc: netdev@vger.kernel.org
Subject: Re: Increased multicast packet drops in 3.4
Date: Thu, 06 Sep 2012 08:26:19 +0200 [thread overview]
Message-ID: <1346912779.13121.178.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120906001108.GA6035@BohrerMBP.rgmadvisors.com>
On Wed, 2012-09-05 at 19:11 -0500, Shawn Bohrer wrote:
> One thing I find interesting is that some of the time 2
> or 3 of the 8 processes will report that they missed the exact same
> 50+ packets. Since the other processes receive the packets I know
> that they are making it to the machine and past the driver.
Could it be that these processes missing 50+ packets provide a non
accessible area of memory and these recvmsg() calls return EFAULT ?
Are you using special memory areas, using mprotect(), or huge pages for
example ?
prev parent reply other threads:[~2012-09-06 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 0:11 Increased multicast packet drops in 3.4 Shawn Bohrer
2012-09-06 6:07 ` Eric Dumazet
2012-09-06 6:22 ` Eric Dumazet
2012-09-06 13:03 ` Shawn Bohrer
2012-09-06 13:21 ` Eric Dumazet
2012-09-06 13:31 ` Eric Dumazet
2012-09-07 4:00 ` Shawn Bohrer
2012-09-07 6:08 ` Eric Dumazet
2012-09-07 22:38 ` Shawn Bohrer
2012-09-06 6:26 ` Eric Dumazet [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=1346912779.13121.178.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sbohrer@rgmadvisors.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