From: Lev Makhlis <mlev@despammed.com>
To: linux-kernel@vger.kernel.org
Subject: TcpOutSegs in tcp_mib not RFC1213 compliant?
Date: Tue, 5 Aug 2003 20:01:22 -0400 [thread overview]
Message-ID: <200308052001.22259.mlev@despammed.com> (raw)
Hi,
>From looking at net/ipv4/tcp_output.c, TcpOutSegs counts all
outgoing packets, including pure retransmits. This seems
to contradict RFC 1213 (MIB-II):
tcpOutSegs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of segments sent, including
those on current connections but excluding those
containing only retransmitted octets."
::= { tcp 11 }
Is that intentional or an oversight?
Lev
reply other threads:[~2003-08-06 0:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308052001.22259.mlev@despammed.com \
--to=mlev@despammed.com \
--cc=linux-kernel@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