From: John Heffner <jheffner@psc.edu>
To: dccp@vger.kernel.org
Subject: Re: [RFC] TCP MTU probing
Date: Wed, 01 Feb 2006 21:40:02 +0000 [thread overview]
Message-ID: <200602011640.02318.jheffner@psc.edu> (raw)
On Monday 30 January 2006 20:21, Ian McDonald wrote:
> On 1/31/06, David S. Miller <davem@davemloft.net> wrote:
> > From: John Heffner <jheffner@psc.edu>
> > Date: Tue, 06 Dec 2005 14:42:53 -0500
> >
> > > I'd like to get a few people at least to look this over, and maybe give
> > > it a try. One remaining item to consider is how best to cache the
> > > state between connections. Are there any major concerns or
> > > reservations about this approach, or the patch itself?
>
> Just having a read of this now (missed first time round) and I see
> that PMTUD as per this RFC is also allowed by DCCP in it's spec
> (Section 14.1).
>
> > and then I'll happily at this in for net-2.6.17
>
> At some future stage we should merge this into the DCCP tree too.
> Looking at the code there are quite a few places where it has TCP in
> there where maybe it would be better to have IP in there to save
> further changes when DCCP starts to use the code....
That would be good. I think SCTP should do this as well. I moved struct mtup
from struct tcp_sock to struct inet_connection_sock. I think most of the
actual code really ends up being pretty protocol-specific though.
-John
next reply other threads:[~2006-02-01 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 21:40 John Heffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-31 1:21 [RFC] TCP MTU probing Ian McDonald
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=200602011640.02318.jheffner@psc.edu \
--to=jheffner@psc.edu \
--cc=dccp@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