From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, edumazet@gmail.com, pabeni@redhat.com,
willemb@google.com, davem@davemloft.net
Subject: Re: UDP sockets oddities
Date: Fri, 25 Aug 2017 18:17:34 -0700 [thread overview]
Message-ID: <ce4af8cc-3de1-a777-967c-a57103994e1d@gmail.com> (raw)
In-Reply-To: <1503705440.11498.9.camel@edumazet-glaptop3.roam.corp.google.com>
On 08/25/2017 04:57 PM, Eric Dumazet wrote:
> On Fri, 2017-08-25 at 16:18 -0700, Florian Fainelli wrote:
>
>> Eric, are there areas of the stack where we are allowed to drop packets,
>> not propagate that back to write(2) and also not increment any counter
>> either, or maybe I am not looking where I should...
>
> What happens if you increase these sysctls ?
I don't see packet loss after I tweak these two sysctls according to
your suggestions.
Tweaking eth0's sysctls did not change anything, but tweaking gphy's
sysctl resolved the loss. This was a little surprising considering that
gphy is an IFF_NO_QUEUE interface and eth0 is the conduit interface that
does the real transmission.
Does that make sense with respect to what I reported earlier? Should I
try to dump the neigh stats?
Thanks!
>
> grep . `find /proc/sys|grep unres_qlen`
>
>
> unres_qlen_bytes -> 2000000
> unres_qlen -> 10000
>
>
--
Florian
next prev parent reply other threads:[~2017-08-26 1:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 20:02 UDP sockets oddities Florian Fainelli
2017-08-23 22:26 ` Eric Dumazet
2017-08-23 22:49 ` Florian Fainelli
2017-08-23 23:04 ` Eric Dumazet
2017-08-24 0:03 ` Florian Fainelli
2017-08-24 0:43 ` Eric Dumazet
2017-08-24 2:23 ` Florian Fainelli
2017-08-25 23:18 ` Florian Fainelli
2017-08-25 23:57 ` Eric Dumazet
2017-08-26 1:17 ` Florian Fainelli [this message]
2017-08-26 1:52 ` Eric Dumazet
2017-08-26 3:25 ` Florian Fainelli
2017-08-26 3:40 ` Eric Dumazet
2017-08-26 4:19 ` David Miller
2017-08-26 12:47 ` Eric Dumazet
2017-08-26 18:56 ` Florian Fainelli
2017-08-29 17:53 ` Florian Fainelli
2017-08-29 18:01 ` Eric Dumazet
2017-08-29 22:16 ` [PATCH net-next] neigh: increase queue_len_bytes to match wmem_default Eric Dumazet
2017-08-29 23:11 ` David Miller
2017-08-29 23:15 ` Eric Dumazet
2017-08-29 23:17 ` David Miller
2017-08-26 4:17 ` UDP sockets oddities David Miller
2017-08-26 5:20 ` Eric Dumazet
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=ce4af8cc-3de1-a777-967c-a57103994e1d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).