netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: Fw: [Bug 199963] New: UDP rx_queue incorrect calculation in /proc/net/udp
Date: Thu, 07 Jun 2018 18:28:47 +0200	[thread overview]
Message-ID: <e99d1e6e54b59831eef6113aff9a740769cf96a7.camel@redhat.com> (raw)
In-Reply-To: <20180607073918.5626370d@xeon-e3>

On Thu, 2018-06-07 at 07:39 -0700, Stephen Hemminger wrote:
> 
> Begin forwarded message:
> 
> Date: Thu, 07 Jun 2018 13:21:23 +0000
> From: bugzilla-daemon@bugzilla.kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 199963] New: UDP rx_queue incorrect calculation in /proc/net/udp
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=199963
> 
>             Bug ID: 199963
>            Summary: UDP rx_queue incorrect calculation in /proc/net/udp
>            Product: Networking
>            Version: 2.5
>     Kernel Version: Kernels >= 4.15
>           Hardware: All
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: IPV4
>           Assignee: stephen@networkplumber.org
>           Reporter: trevor.francis@46labs.com
>         Regression: No
> 
> since upgrading to any kernel >= 4.15 the rx_queue in /proc/net/udp is now
> reporting a queue, regardless of system load and regardless of what
> applications are running on it. The tx_queue is always 0, but rx_queue has
> seemingly random spikes of udp queueing. This is observed across hundreds of
> servers with either varying or no workload.
> 
> netstat -nl|grep ^udp
> udp 4352 0 0.0.0.0:68 0.0.0.0:*
> 
> sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid
> timeout inode ref pointer drops
> 14645: 3500007F:0035 00000000:0000 07 00000000:0000C900 00:00000000 00000000
> 101 0 3367 2 ffff8da177fdcc00 0

after:

commit 0d4a6608f68c7532dcbfec2ea1150c9761767d03
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Tue Sep 19 12:11:43 2017 +0200

    udp: do rmem bulk free even if the rx sk queue is empty

rmem can be a non-0, small, value even if the rx queue is empty,
because it reports the (forward) allocated memory for this socket, not
the queue length in bytes. 

I'll cook a patch to fix the above.

Cheers,

Paolo

      reply	other threads:[~2018-06-07 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 14:39 Fw: [Bug 199963] New: UDP rx_queue incorrect calculation in /proc/net/udp Stephen Hemminger
2018-06-07 16:28 ` Paolo Abeni [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=e99d1e6e54b59831eef6113aff9a740769cf96a7.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).