nginx mss patch

[Ning Wang]

some wireless home router's mtu parameter was not set up correctly, and we
have to use this patch to indicate end users to send a smaller  package.
However this feature does not function below kernel version 2.6.28.

On Mon, Jun 13, 2011 at 4:43 PM, Ning Wang <renren.wangning at gmail.com>wrote:

> the new mss patch. TCP_MAXSEG value is not set by default.
>
> the previous one was generated using git diff, hopefully the format is
> right this time.
>
>
>
> On Thu, Jun 9, 2011 at 3:20 PM, Igor Sysoev <igor at sysoev.ru> wrote:
>
>> On Thu, Jun 09, 2011 at 01:10:00PM +0800, Joshua Zhu wrote:
>> > Hi,
>> >
>> > Just out of curiosity, could you please provide some context, i.e. in
>> what
>> > circumstance do you have to change the TCP MSS or the benefit? After
>> all,
>> > there're TCP path MTU discovery mechanisms already.
>> >
>> > As for the patch itself, I don't think it's a good idea to set the
>> default
>> > value of mss to 1024, since it will punish those who don't want this
>> > feature. BTW, the TCP_MAXSEG option is not supported by all OS vendors,
>> so
>> > you should test it first (in auto/os/features).
>>
>> Yes, the default TCP_MAXSEG value should not be set, and
>> should be handled like rcvbuf or sndbuf option.
>>
>>
>> --
>> Igor Sysoev
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://nginx.org/mailman/listinfo/nginx
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110619/26681269/attachment.html>