From: David Miller <davem@davemloft.net>
To: mcmanus@ducksong.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/3 resend] TCP_DEFER_ACCEPT updates - defer timeout conflicts with max_thresh
Date: Fri, 21 Mar 2008 16:28:21 -0700 (PDT) [thread overview]
Message-ID: <20080321.162821.225728823.davem@davemloft.net> (raw)
In-Reply-To: <1206053738.13044.21.camel@tng>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Thu, 20 Mar 2008 18:55:38 -0400
> commit 077b5f8e36b93e5121f680c3bb327e7464020fd2
> Author: Patrick McManus <mcmanus@ducksong.com>
> Date: Sat Feb 23 12:23:47 2008 -0500
>
> timeout associated with SO_DEFER_ACCEPT wasn't being honored if it was
> less than the timeout allowed by the maximum syn-recv queue size
> algorithm. Fix by using the SO_DEFER_ACCEPT value if the ack has
> arrived.
>
> Signed-off-by: Patrick McManus <mcmanus@ducksong.com>
> Acked-by: Eric Dumazet <dada1@cosmosbay.com>
Applied to net-2.6.26, thanks.
prev parent reply other threads:[~2008-03-21 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 22:55 [PATCH 1/3 resend] TCP_DEFER_ACCEPT updates - defer timeout conflicts with max_thresh Patrick McManus
2008-03-20 23:17 ` David Miller
2008-03-21 23:28 ` David Miller [this message]
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=20080321.162821.225728823.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mcmanus@ducksong.com \
--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 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).