From: David Miller <davem@davemloft.net>
To: apetlund@simula.no
Cc: netdev@vger.kernel.org, ilpo.jarvinen@helsinki.fi,
eric.dumazet@gmail.com, hannemann@nets.rwth-aachen.de,
linux-kernel@vger.kernel.org, shemminger@vyatta.com,
william.allen.simpson@gmail.com, damian@tvk.rwth-aachen.de,
ebiederm@xmission.com, franco@lastsummer.de
Subject: Re: [net-next PATCH v5 0/3] net: TCP thin-stream latency-improving modifications
Date: Thu, 18 Feb 2010 15:43:45 -0800 (PST) [thread overview]
Message-ID: <20100218.154345.28706204.davem@davemloft.net> (raw)
In-Reply-To: <4B7D35A5.10106@simula.no>
From: Andreas Petlund <apetlund@simula.no>
Date: Thu, 18 Feb 2010 13:42:13 +0100
> This is a series of patches enabling non-intrusive, dynamically
> triggered modifications that improve retransmission latencies
> for thin streams.
>
> The patch set was modified according to the feedback received.
>
> Major change:
> -Used bitfields to compact the nonagle variable
> in the tcp_sock struct. nonagle, thin_lto and
> thin_dupack is now contained in the same u8.
>
> I decided to use bitfields to handle this as it is
> already done similarly in the tcp_options_received struct.
>
> Also corrected some formatting issues.
All applied (I made sure the get the updated version of patch #3),
thanks a lot!
prev parent reply other threads:[~2010-02-18 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 12:42 [net-next PATCH v5 0/3] net: TCP thin-stream latency-improving modifications Andreas Petlund
2010-02-18 12:45 ` [net-next PATCH v5 1/3] net: TCP thin-stream detection Andreas Petlund
2010-02-18 12:47 ` [net-next PATCH v5 2/3] net: TCP thin linear timeouts Andreas Petlund
2010-02-18 12:48 ` [net-next PATCH v5 3/3] net: TCP thin dupack Andreas Petlund
2010-02-18 12:56 ` Ilpo Järvinen
2010-02-18 14:48 ` [net-next PATCH v5.1 " Andreas Petlund
2010-02-18 23:43 ` 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=20100218.154345.28706204.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=apetlund@simula.no \
--cc=damian@tvk.rwth-aachen.de \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=franco@lastsummer.de \
--cc=hannemann@nets.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=william.allen.simpson@gmail.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 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).