From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: "Adam Langley" <agl@imperialviolet.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] TCP: Add seq and ack numbers to TCP_INFO
Date: Wed, 9 Jul 2008 10:49:34 -0700 [thread overview]
Message-ID: <20080709104934.390cd81b@speedy> (raw)
In-Reply-To: <396556a20805301217k293e5718h6bbf02bfe069003@europa>
On Wed, 9 Jul 2008 10:23:43 -0700
"Adam Langley" <agl@imperialviolet.org> wrote:
> TCP: Add seq and ack numbers to TCP_INFO
>
> No ABI breakage: Userspace specifies the size of the structure that they're
> expecting, and the new fields are at the end, so existing code should function
> just fine as we'll truncate the new struct tcp_info to fit.
>
> Signed-off-by: Adam Langley <agl@imperialviolet.org>
Of what possible use is this to an application? I worry that applications would
come to expect or use certain characteristics of the network and TCP which
would be broken by later changes.
next prev parent reply other threads:[~2008-07-09 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 17:23 [PATCH] TCP: Add seq and ack numbers to TCP_INFO Adam Langley
2008-07-09 17:49 ` Stephen Hemminger [this message]
2008-07-09 18:02 ` Adam Langley
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=20080709104934.390cd81b@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=agl@imperialviolet.org \
--cc=davem@davemloft.net \
--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 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.