netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev@oss.sgi.com
Subject: Re: Assertions when lowering tcp_tso_win_divisor
Date: Tue, 16 Nov 2004 10:47:55 -0800	[thread overview]
Message-ID: <20041116104755.32bdb7a7.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0411160931080.31882@w-sridhar.beaverton.ibm.com>

On Tue, 16 Nov 2004 09:47:14 -0800 (PST)
Sridhar Samudrala <sri@us.ibm.com> wrote:

> We are seeing following assertions when running specweb99 with
> tcp_tso_win_divisor lowered to 4, 2 or 1 on linux 2.6.9 based kernels.
> 
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (152)
> 
> looks like an issue with the accounting of sk_forward_alloc with non-default
> values of tcp_tso_win_divisor.

The issue is if you change the value while there are still existing
sockets which used a previous value at least once.

Looks like we'll have to cache this inside of the per-socket structure
to fix this bug, but realize that once I do that the new sysctl value
will not apply to any existing TCP sockets and this will effect your
testing.  So for example, if the web server was started with one particular
value of the sysctl, no matter how many times you change the sysctl after-
wards, the old original sysctl value will be used for every web server
connection made to the machine.

  reply	other threads:[~2004-11-16 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 17:47 Assertions when lowering tcp_tso_win_divisor Sridhar Samudrala
2004-11-16 18:47 ` David S. Miller [this message]
2004-11-16 20:39   ` Herbert Xu
2004-11-17  0:31     ` David S. Miller
2004-11-16 20:59 ` Herbert Xu
2004-11-17  0:31   ` David S. Miller
2004-11-20  2:00     ` Sridhar Samudrala
2004-11-20  6:35       ` David S. Miller
2004-11-20 23:19         ` Sridhar Samudrala
2004-11-21  0:44           ` Arnaldo Carvalho de Melo
2004-11-21  3:25           ` David S. 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=20041116104755.32bdb7a7.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=sri@us.ibm.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).