From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: ycheng@google.com, ncardwell@google.com, nanditad@google.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: detect loss above high_seq in recovery
Date: Wed, 28 Dec 2011 13:07:36 -0500 (EST) [thread overview]
Message-ID: <20111228.130736.79570418506453470.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1112281736480.7752@melkinpaasi.cs.helsinki.fi>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Wed, 28 Dec 2011 17:42:06 +0200 (EET)
> I don't think you can remove MIBs as they're userspace visible.
Because of how they are implemented and how applications use them,
this is actually allowed.
All the MIBs are presented first as a series of strings, then as a
series of values.
So applications parse them both to report the statistics, and this do
get coded in a way that they do not need to assume the presence or
particular ordering of these MIBS.
Therefore, such a change is safe.
next prev parent reply other threads:[~2011-12-28 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 0:46 [PATCH] tcp: detect loss above high_seq in recovery Yuchung Cheng
2011-12-28 15:42 ` Ilpo Järvinen
2011-12-28 18:07 ` David Miller [this message]
2011-12-29 18:21 ` Yuchung Cheng
2011-12-30 11:19 ` Ilpo Järvinen
2012-01-03 18:54 ` Yuchung Cheng
2012-01-03 19:11 ` Ilpo Järvinen
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=20111228.130736.79570418506453470.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=nanditad@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).