From owner-freebsd-hackers@FreeBSD.ORG  Sat Sep 14 01:39:10 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@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 ESMTP id 588CE92D;
 Sat, 14 Sep 2013 01:39:10 +0000 (UTC)
 (envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca
 [131.104.91.36])
 by mx1.freebsd.org (Postfix) with ESMTP id 8B6B92916;
 Sat, 14 Sep 2013 01:39:08 +0000 (UTC)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAP+9M1KDaFve/2dsb2JhbABbgz9Sgyq9U4E1dIIlAQEEASNWBRYYAgINGQJZBgqIBgYMp2aRc4EpjhQ0B4JpgTUDhRWWbY1sg0AggW4
X-IronPort-AV: E=Sophos;i="4.90,902,1371096000"; d="scan'208";a="51799604"
Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca)
 ([131.104.91.222])
 by esa-annu.net.uoguelph.ca with ESMTP; 13 Sep 2013 21:38:50 -0400
Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1])
 by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 67F6EB404B;
 Fri, 13 Sep 2013 21:38:50 -0400 (EDT)
Date: Fri, 13 Sep 2013 21:38:50 -0400 (EDT)
From: Rick Macklem <rmacklem@uoguelph.ca>
To: "Sam Fourman Jr." <sfourman@gmail.com>
Message-ID: <1087948919.23486338.1379122730412.JavaMail.root@uoguelph.ca>
In-Reply-To: <CAOFF+Z0afxp+ZyD9+mFmoMopfXSSaZ10t2i3fJMwEPxi278R+w@mail.gmail.com>
Subject: Re: Network stack changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.91.202]
X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790)
X-Mailman-Approved-At: Sat, 14 Sep 2013 11:18:56 +0000
Cc: "Alexander V. Chernikov" <melifaro@yandex-team.ru>,
 Luigi Rizzo <luigi@freebsd.org>, Andre Oppermann <andre@freebsd.org>,
 freebsd-hackers@freebsd.org, George Neville-Neil <gnn@neville-neil.com>,
 freebsd-arch@freebsd.org, Adrian Chadd <adrian@freebsd.org>,
 "Andrey V. Elsukov" <ae@freebsd.org>, Gleb Smirnoff <glebius@freebsd.org>,
 FreeBSD Net <net@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2013 01:39:10 -0000

Sam Fourman Jr. wrote:
> >
> 
> > And any time you increase latency, that will have a negative impact
> > on
> > NFS performance. NFS RPCs are usually small messages (except Write
> > requests
> > and Read replies) and the RTT for these (mostly small,
> > bidirectional)
> > messages can have a significant impact on NFS perf.
> >
> > rick
> >
> >
> this may be a bit off topic but not much... I have wondered with all
> of the
> new
> tcp algorithms
> http://freebsdfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-congestion.html
> 
> what algorithm is best suited for NFS over gigabit Ethernet, say
> FreeBSD to
> FreeBSD.
> and further more would a NFS optimized tcp algorithm be useful?
> 
I have no idea what effect they might have. NFS traffic is quite different than
streaming or bulk data transfer. I think this might make a nice research
project for someone.

rick

> Sam Fourman Jr.
>