From: Andi Kleen <andi@firstfloor.org>
To: Salvador Fandino <salvador@qindel.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@firstfloor.org, "@vger.kernel.org"@firstfloor.org
Subject: Re: [PATCH] allow to configure tcp_retries1 and tcp_retries2 per TCP socket
Date: Thu, 10 Jun 2010 19:00:19 +0200 [thread overview]
Message-ID: <87bpbi4ycc.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1276186161.2419.10.camel@topo> (Salvador Fandino's message of "Thu\, 10 Jun 2010 18\:09\:21 +0200")
Salvador Fandino <salvador@qindel.com> writes:
> The included patch adds support for setting the tcp_retries1 and
> tcp_retries2 options in a per socket fashion as it is done for the
> keepalive options TCP_KEEPIDLE, TCP_KEEPCNT and TCP_KEEPINTVL.
>
> The issue I am trying to solve is that when a socket has data queued for
> delivering, the keepalive logic is not triggered. Instead, the
> tcp_retries1/2 parameters are used to determine how many delivering
> attempts should be performed before giving up.
And why exactly do you need new tunables to solve this?
>
> The patch is very straight forward and just replicates similar
> functionality. There is one thing I am not completely sure and is if the
> new per-socket fields should go into inet_connection_sock instead of
> into tcp_sock.
tcp_sock is already quite big (>2k on 64bit)
IMHO any new fields in there need very good justification.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-06-10 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 16:09 [PATCH] allow to configure tcp_retries1 and tcp_retries2 per TCP socket Salvador Fandino
2010-06-10 17:00 ` Andi Kleen [this message]
2010-06-11 10:43 ` Salvador Fandino
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=87bpbi4ycc.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc="@vger.kernel.org"@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@firstfloor.org \
--cc=netdev@vger.kernel.org \
--cc=salvador@qindel.com \
/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.