mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
To: Andreas Petlund <apetlund@simula.no>
Cc: linux-kernel@vger.kernel.org,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
Date: Thu, 04 Dec 2008 04:15:50 -0800	[thread overview]
Message-ID: <1228392950.9704.4.camel@sven.thebigcorporation.com> (raw)
In-Reply-To: <492EA31D.8000704@simula.no>

On Thu, 2008-11-27 at 14:39 +0100, Andreas Petlund wrote:

Hi -

Just a minor nit (trying your patch on a 2.6.22 Kernel):

These little white space tweaks are to be avoided, adding to the patch
size unnecessarily.

Do you have a version against 2.6.28, or Linux-tip?

Regards,

Sven

>                 }
> -
> +               
>                 /* Initial outgoing SYN's get put onto the write_queue
>                  * just like anything else we transmit.  It is not
>                  * true data, and if we misinform our callers that
> @@ -2479,14 +2585,14 @@
>                         acked |= FLAG_SYN_ACKED;
>                         tp->retrans_stamp = 0;
>                 }
> -
> +               
>                 /* MTU probing checks */
>                 if (icsk->icsk_mtup.probe_size) {
>                         if (!after(tp->mtu_probe.probe_seq_end,
> TCP_SKB_CB(skb)->end_seq)) {
>                                 tcp_mtup_probe_success(sk, skb);
>                         }
>                 }
> -
> +               
>                 if (sacked) {
>                         if (sacked & TCPCB_RETRANS) {
>                                 if (sacked & TCPCB_SACKED_RETRANS)
> @@ -2510,24 +2616,32 @@


  parent reply	other threads:[~2008-12-04 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 13:39 Andreas Petlund
2008-11-28 12:25 ` Ilpo Järvinen
2008-12-04 12:15 ` Sven-Thorsten Dietrich [this message]
2009-01-12 14:54 Andreas Petlund
2009-01-14 15:32 ` Ilpo Järvinen
2009-01-16 10:13   ` kristrev

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=1228392950.9704.4.camel@sven.thebigcorporation.com \
    --to=sven@thebigcorporation.com \
    --cc=apetlund@simula.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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

all inboxes | Powered by JetHome®