[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1391879318.10160.108.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Sat, 08 Feb 2014 09:08:38 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Thomas Glanzmann <thomas@...nzmann.de>
Cc: John Ogness <john.ogness@...utronix.de>,
Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
"Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
target-devel <target-devel@...r.kernel.org>,
Linux Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: REGRESSION f54b311142a92ea2e42598e347b84e1655caf8e3 tcp auto
corking slows down iSCSI file system creation by factor of 70 [WAS: 4 TB
VMFS creation takes 15 minutes vs 26 seconds]
On Sat, 2014-02-08 at 17:57 +0100, Thomas Glanzmann wrote:
> Hello Eric,
>
> > Note : We did some patches in the MSG_MORE logic for sendpage(), but
> > in your case I do not think its related
> > (git grep -n MSG_SENDPAGE_NOTLAST ) if you are curious
>
> thank you for the pointer. The iSCSI target code actually uses sendpage
> whenever it can.
Yep, but the problem (at least on your pcap), is about sending the 48
bytes headers in TCP segment of its own, then the 512 byte payload in a
separate segment.
I suspect the sendpage() is only used for the payload. No need for
MSG_MORE here.
The MSG_MORE would need to be set on the first part (48 bytes header),
so that TCP stack will defer the push of the segment at the time the 512
bytes payload is added.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists