All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sharat Masetty <sharat04@gmail.com>
Cc: chptx y <chptxy@gmail.com>, Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: What causes these TCP packet getting lost in linux kernel
Date: Sat, 12 Apr 2014 12:32:52 -0700	[thread overview]
Message-ID: <1397331172.4222.8.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAJzFV35Z9f-73of0vq2bhUZbN++17cuexcQV4SSSvqJXNyKnRQ@mail.gmail.com>

On Sat, 2014-04-12 at 12:35 -0600, Sharat Masetty wrote:
> Check /proc/net/netstat and /proc/net/snmp
> 
> In netstat look for
> 
> LINUX_MIB_TCPOFODROP and LINUX_MIB_BACKLOGDROP

The packet is not out of order, according to tcpdump.

Note that the receiver reacts to incoming packet, sending a DUPACK, so
its not a backlogdrop.

tcpdump trace is really incomplete, I asked tcpdump -vv but got nothing
from chptx, assuming this is a real name.

packet might be rejected because of a zero receiver window, who knows.

I might search in my basement this crystal ball I might have.

  reply	other threads:[~2014-04-12 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  7:19 What causes these TCP packet getting lost in linux kernel chptx y
2014-04-11 10:41 ` Eric Dumazet
2014-04-12  3:06   ` chptx y
2014-04-12 18:35     ` Sharat Masetty
2014-04-12 19:32       ` Eric Dumazet [this message]
2014-04-14  5:02         ` chptx y
2014-04-14  5:27           ` Eric Dumazet
2014-04-14  6:00             ` chptx y
2014-04-14  8:39           ` David Newall
2014-04-14  9:20             ` chptx y
2014-04-14 14:13               ` Eric Dumazet
2014-04-14 17:58                 ` Sharat Masetty
2014-04-14 18:32                   ` 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=1397331172.4222.8.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=chptxy@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sharat04@gmail.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 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.