From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 5/7] [DCCP]: Introduce two new socket options
Date: Thu, 16 Nov 2006 14:07:16 +0000 [thread overview]
Message-ID: <200611161407.16950@strip-the-willow> (raw)
In-Reply-To: <200609221430.14555.ian.mcdonald@jandi.co.nz>
Quoting Arnaldo Carvalho de Melo:
| On 9/22/06, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
| > Quoting Eddie Kohler:
| > | > Why burden the application programmer to handcode an estimation of the average each
| > | > time? I can not see a justification for this, certainly not for CCIDs which
| > | > are intended to be used with (on average) fixed packet sizes.
| > | >
| > | > I think that a priority is to keep the user programming interface as simple as
| > | > possible -- like UDP's interface, as stated in RFC 4340.
| > |
| > | But if DCCP_SOCKOPT_TX_PACKET_SIZE defaults to the MSS, which the drafts
| > | explicitly allow, then there's no burden on the application programmer.
| > This is a good input and should be related to patch 6/7 in which the default setting is
| > the standard size packet of 256 bytes; so maybe we should use MSS (or an estimate of it) there.
|
| Hi Folks, could Ian or Gerrit respin these patches to reflect what was
| discussed here? Perhaps we can get this merged in 2.6.20 if we get
| this done and tested before the merge window closes.
I am working on this, hope to have patch ready by end of next week.
Gerrit
next prev parent reply other threads:[~2006-11-16 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 2:30 [PATCH 5/7] [DCCP]: Introduce two new socket options Ian McDonald
2006-09-22 2:30 ` Ian McDonald
2006-09-22 10:37 ` Gerrit Renker
2006-09-22 10:37 ` Gerrit Renker
2006-09-22 16:56 ` Eddie Kohler
2006-09-22 16:56 ` Eddie Kohler
2006-09-22 17:28 ` Gerrit Renker
2006-09-22 17:35 ` Eddie Kohler
2006-09-22 17:49 ` Gerrit Renker
2006-11-16 13:57 ` Arnaldo Carvalho de Melo
2006-11-16 14:07 ` Gerrit Renker [this message]
2006-11-16 14:09 ` Arnaldo Carvalho de Melo
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=200611161407.16950@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--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 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.