From: David Miller <davem@davemloft.net>
To: rick.jones2@hp.com
Cc: eparis@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: export the number of times the recv queue was full
Date: Thu, 10 Dec 2009 13:48:07 -0800 (PST) [thread overview]
Message-ID: <20091210.134807.54217873.davem@davemloft.net> (raw)
In-Reply-To: <4B216A61.7020704@hp.com>
From: Rick Jones <rick.jones2@hp.com>
Date: Thu, 10 Dec 2009 13:38:41 -0800
> Eric Paris wrote:
>> We got a request in which a customer was trying to determine how often
>> their
>> recieve queue was full and thus they were sending a zero window back
>> to the
>> other side. By the time they would notice the slowdowns they would
>> have all
>> empty receive queues and wouldn't know which socket was a problem.
>
> Wouldn't a tcpdump command with suitable filter expression on the
> window field of the TCP header do?
>
>> It also
>> allows them to find the sockets in which they need to up the recv
>> queue size
>> rather than doing it for all sockets across the box.
>
> Doesn't Linux by default "autotune" the socket buffers? (Or perhaps is
> that how they got zero windows from time to time anyway?)
The window will "autotune" only if the connection is not application
limited.
Their applications, therefore, by definition are getting filled up
receive queues because it is busy doing something other than reading
from the socket when data arrives (disk I/Os, etc.)
next prev parent reply other threads:[~2009-12-10 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 21:09 [PATCH] net: export the number of times the recv queue was full Eric Paris
2009-12-10 21:38 ` Rick Jones
2009-12-10 21:48 ` David Miller [this message]
2009-12-10 21:52 ` Eric Paris
2009-12-10 22:02 ` David Miller
2009-12-10 22:13 ` Rick Jones
2009-12-10 21:49 ` David Miller
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=20091210.134807.54217873.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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.