From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next] net: More verbose message for too-many-orphans.
Date: Tue, 10 Aug 2010 01:48:01 -0700 (PDT) [thread overview]
Message-ID: <20100810.014801.212696050.davem@davemloft.net> (raw)
In-Reply-To: <1281380402-14608-1-git-send-email-greearb@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Mon, 9 Aug 2010 12:00:02 -0700
> The original message doesn't give much clue as to what
> is actually going wrong or how to fix it.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
Dumping a bunch of values obtainable via sysctl is pointless.
The only non-sysctl value you're dumping is 'orphans' and based upon
the sysctl values you can determine whether it made the check inside
of tcp_too_many_orphans() trigger, and in what way.
I'm not applying this, sorry.
prev parent reply other threads:[~2010-08-10 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 19:00 [net-next] net: More verbose message for too-many-orphans Ben Greear
2010-08-10 8:48 ` David Miller [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=20100810.014801.212696050.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.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).