[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061129154200.c4db558c.akpm@osdl.org>
Date: Wed, 29 Nov 2006 15:42:00 -0800
From: Andrew Morton <akpm@...l.org>
To: wenji@...l.gov
Cc: netdev@...r.kernel.org, davem@...emloft.net,
linux-kernel@...r.kernel.org
Subject: Re: Bug 7596 - Potential performance bottleneck for Linxu TCP
On Wed, 29 Nov 2006 17:22:10 -0600
Wenji Wu <wenji@...l.gov> wrote:
> From: Wenji Wu <wenji@...l.gov>
>
> Greetings,
>
> For Linux TCP, when the network applcaiton make system call to move data
> from
> socket's receive buffer to user space by calling tcp_recvmsg(). The socket
> will
> be locked. During the period, all the incoming packet for the TCP socket
> will go
> to the backlog queue without being TCP processed. Since Linux 2.6 can be
> inerrupted mid-task, if the network application expires, and moved to the
> expired array with the socket locked, all the packets within the backlog
> queue
> will not be TCP processed till the network applicaton resume its execution.
> If
> the system is heavily loaded, TCP can easily RTO in the Sender Side.
>
> Attached is the detailed description of the problem and one possible
> solution.
Thanks. The attachment will be too large for the mailing-list servers so I
uploaded a copy to
http://userweb.kernel.org/~akpm/Linux-TCP-Bottleneck-Analysis-Report.pdf
>From a quick peek it appears that you're getting around 10% improvement in
TCP throughput, best case.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists