From: Eric Dumazet <eric.dumazet@gmail.com>
To: Daniel Baluta <dbaluta@ixiacom.com>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [RFC] tcp: Export TCP Delayed ACK parameters to user
Date: Fri, 28 Oct 2011 02:01:37 +0200 [thread overview]
Message-ID: <1319760097.19125.55.camel@edumazet-laptop> (raw)
In-Reply-To: <1319756841-2051-1-git-send-email-dbaluta@ixiacom.com>
Le vendredi 28 octobre 2011 à 02:07 +0300, Daniel Baluta a écrit :
> RFC2581 ($4.2) specifies when an ACK should be generated as follows:
>
> " .. an ACK SHOULD be generated for at least every second
> full-sized segment, and MUST be generated within 500 ms
> of the arrival of the first unacknowledged packet.
> "
>
> We export the number of segments and the timeout limits
> specified above, so that a user can tune them according
> to its needs.
>
Well, this requires user has a machine exclusive use :)
> Specifically:
> * /proc/sys/net/ipv4/tcp_delack_segs, represents
> the threshold for the number of segments.
> * /proc/sys/net/ipv4/tcp_delack_min, specifies
> the minimum timeout value
> * /proc/sys/net/ipv4/tcp_delack_max, specifies
> the maximum timeout value.
>
> Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
> ---
> include/net/tcp.h | 20 +++++++++++++++++---
> net/ipv4/sysctl_net_ipv4.c | 21 +++++++++++++++++++++
> net/ipv4/tcp.c | 5 +++--
> net/ipv4/tcp_input.c | 7 +++++--
> net/ipv4/tcp_output.c | 4 +++-
> 5 files changed, 49 insertions(+), 8 deletions(-)
>
Missing Documentation changes
> diff --git a/include/net/tcp.h b/include/net/tcp.h
> index e147f42..f3b0c17 100644
> --- a/include/net/tcp.h
> +++ b/include/net/tcp.h
> @@ -111,14 +111,21 @@ extern void tcp_time_wait(struct sock *sk, int state, int timeo);
> * TIME-WAIT timer.
> */
>
> -#define TCP_DELACK_MAX ((unsigned)(HZ/5)) /* maximal time to delay before sending an ACK */
> +/* default maximum time to delay before sending an ACK */
> +#define TCP_DELACK_MAX_DEFAULT ((unsigned)(HZ/5))
> +
> #if HZ >= 100
> -#define TCP_DELACK_MIN ((unsigned)(HZ/25)) /* minimal time to delay before sending an ACK */
> +/* default minimum time to delay before sending an ACK */
> +#define TCP_DELACK_MIN_DEFAULT ((unsigned)(HZ/25))
> #define TCP_ATO_MIN ((unsigned)(HZ/25))
> #else
> -#define TCP_DELACK_MIN 4U
> +#define TCP_DELACK_MIN_DEFAULT 4U
> #define TCP_ATO_MIN 4U
> #endif
> +
> +#define TCP_DELACK_MIN sysctl_tcp_delack_min
> +#define TCP_DELACK_MAX sysctl_tcp_delack_max
Hmm, please try to compile dccp as a module :)
You need some EXPORT_SYMBOL() definitions.
Frankly, I suggest removing TCP_DELACK_{MIN|MAX} to avoid unecessary
layer, and use sysctl_tcp_delack_{min|max} instead
> +
> #define TCP_RTO_MAX ((unsigned)(120*HZ))
> #define TCP_RTO_MIN ((unsigned)(HZ/5))
> #define TCP_TIMEOUT_INIT ((unsigned)(1*HZ)) /* RFC2988bis initial RTO value */
> @@ -251,6 +258,9 @@ extern int sysctl_tcp_max_ssthresh;
> extern int sysctl_tcp_cookie_size;
> extern int sysctl_tcp_thin_linear_timeouts;
> extern int sysctl_tcp_thin_dupack;
> +extern int sysctl_tcp_delack_segs;
> +extern int sysctl_tcp_delack_min;
> +extern int sysctl_tcp_delack_max;
>
> extern atomic_long_t tcp_memory_allocated;
> extern struct percpu_counter tcp_sockets_allocated;
> @@ -1557,6 +1567,10 @@ static inline struct tcp_extend_values *tcp_xv(struct request_values *rvp)
> {
> return (struct tcp_extend_values *)rvp;
> }
> +static inline int tcp_snd_thresh(struct sock *sk)
I am not sure name is properly chosen, its about delack or not ?
const struct *sk
> +{
> + return inet_csk(sk)->icsk_ack.rcv_mss * sysctl_tcp_delack_segs;
> +}
>
Thanks !
next prev parent reply other threads:[~2011-10-28 0:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 23:07 [RFC] tcp: Export TCP Delayed ACK parameters to user Daniel Baluta
2011-10-28 0:01 ` Eric Dumazet [this message]
2011-10-28 8:01 ` Daniel Baluta
2011-10-28 8:44 ` Eric Dumazet
2011-10-28 16:38 ` Rick Jones
2011-10-28 21:14 ` [RFC v2] " Daniel Baluta
2011-10-28 21:19 ` David Miller
2011-10-28 21:35 ` Daniel Baluta
2011-10-28 22:31 ` David Miller
2011-10-28 22:40 ` Rick Jones
2011-10-29 2:24 ` David Miller
2011-10-29 12:32 ` Daniel Baluta
2011-10-30 4:13 ` David Miller
2011-10-31 18:10 ` Rick Jones
2011-10-31 20:02 ` Daniel Baluta
2011-10-31 21:29 ` Rick Jones
2011-10-28 21:53 ` Andy Lutomirski
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=1319760097.19125.55.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dbaluta@ixiacom.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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