From owner-freebsd-net@FreeBSD.ORG Fri Mar 28 02:22:59 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60AAE3E4; Fri, 28 Mar 2014 02:22:59 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1CEA9DC; Fri, 28 Mar 2014 02:22:58 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id k14so3072483wgh.34 for ; Thu, 27 Mar 2014 19:22:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NPFp+tus8ErKwhknLJ2A80qU2/J7j8uPgzmKaAojwWg=; b=Dr11GtEjnRUDTfSDjzEGC4qxB1Xv26RlhLjVxSPSlIYIjeZa4dka4uC98KyHP97ciK KC80mqUi/WOUxJjsQj6E2sUFPPOt0o75XgsB9RQq/Z8qSl7U3BM52Ahz29RsNjh50nXp 29Qiz163E4mIYq3aduNJxSi8OIrsi7DRrTX43e0fmN7VTPnpfmnZ76mEiNkCngD3LtfH 37wi2Q/2KohBbne0f90BNP2AOG8/jLJed1VgWW92zaEwgQcLgTleXuTWeaHju4j+P0T5 zGCDWhDG5cH4YFYPS+y+uzbcLVuVheQlrEX4ii9l9LNm8QC7hPZf907WiRjVB3JtBUPL B0pQ== MIME-Version: 1.0 X-Received: by 10.180.94.196 with SMTP id de4mr9118830wib.16.1395973376922; Thu, 27 Mar 2014 19:22:56 -0700 (PDT) Received: by 10.216.190.199 with HTTP; Thu, 27 Mar 2014 19:22:56 -0700 (PDT) In-Reply-To: <380071870.1832898.1395956256461.JavaMail.root@uoguelph.ca> References: <380071870.1832898.1395956256461.JavaMail.root@uoguelph.ca> Date: Fri, 28 Mar 2014 10:22:56 +0800 Message-ID: Subject: Re: RFC: How to fix the NFS/iSCSI vs TSO problem From: Marcelo Araujo To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: pyunyh@gmail.com, FreeBSD Filesystems , Alexander Motin , FreeBSD Net , Christopher Forgeron X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 02:22:59 -0000 2014-03-28 5:37 GMT+08:00 Rick Macklem : > Christopher Forgeron wrote: > > I'm quite sure the problem is on 9.2-RELEASE, not 9.1-RELEASE or > > earlier, > > as a 9.2-STABLE from last year I have doesn't exhibit the problem. > > New > > code in if.c at line 660 looks to be what is starting this, which > > makes me > > wonder how TSO was being handled before 9.2. > > > > I also like Rick's NFS patch for cluster size. I notice an > > improvement, but > > don't have solid numbers yet. I'm still stress testing it as we > > speak. > > > Unfortunately, this causes problems for small i386 systems, so I > am reluctant to commit it to head. Maybe a variant that is only > enabled for amd64 systems with lots of memory would be ok? > > Rick, Maybe you can create a SYSCTL to enable/disable it by the end user will be more reasonable. Also, of course, it is so far safe if only 64Bits CPU can enable this SYSCTL. Any other option seems not OK, will be hard to judge what is lots of memory and what is not, it will depends what is running onto the system. The SYSCTL will be great, and in case you don't have time to do it, I can give you a hand. I'm gonna do more benchmarks today and will send another report, but in our product here, I'm inclined to use this patch, because 10~20% speed up in read for me is a lot. :-) Thank you so much and best regards, -- Marcelo Araujo araujo@FreeBSD.org