From owner-freebsd-net@FreeBSD.ORG Sat Sep 14 03:20:11 2013 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C15D375C; Sat, 14 Sep 2013 03:20:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77D232D5A; Sat, 14 Sep 2013 03:20:10 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id b13so1846169wgh.23 for ; Fri, 13 Sep 2013 20:20:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=IFtRksCRmfL5B1+1wrQ7GTfCJsIIDDCQHX1+tZW4pFQ=; b=gI6Nxi2aoExXobnlohogoRzOt/qT7IXI0S9dphpVrKUea7aD4TIXmx63GGGEDMC1RJ RA27fo4BQDJ0VIiHocD9bvG5E37i8JnwODvAUpXEJn2OAIBJ2JGT6jwZfTwYLig5VAjm J7TZj0nj1NWZi1FqKh2SoMOjG0roERH3UT+4AbsBozTVV0yA36ecQqdvoYj2OkHeN4XN eB7iFW8OKSUD1qX1mVZhJ/ELCZNLJTkM8J5BBS8MQf192G62xmiN8QUTJ8ANiHntSpYH SC1bDAPmy6yBesJBrzoElWyK5AJ9DmzUj9+jkqOACAjjYPgoMyEzracI7lwUC/CdcGkW UZrQ== MIME-Version: 1.0 X-Received: by 10.180.10.136 with SMTP id i8mr4954841wib.46.1379128808906; Fri, 13 Sep 2013 20:20:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Fri, 13 Sep 2013 20:20:08 -0700 (PDT) In-Reply-To: <221093226.23439826.1379112203059.JavaMail.root@uoguelph.ca> References: <6BDA4619-783C-433E-9819-A7EAA0BD3299@neville-neil.com> <221093226.23439826.1379112203059.JavaMail.root@uoguelph.ca> Date: Fri, 13 Sep 2013 20:20:08 -0700 X-Google-Sender-Auth: A0kv2cAHQtkyVSyFBvksPLrnLYs Message-ID: Subject: Re: Network stack changes From: Adrian Chadd To: Rick Macklem X-Mailman-Approved-At: Sat, 14 Sep 2013 12:12:53 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Alexander V. Chernikov" , Luigi Rizzo , Andre Oppermann , "freebsd-hackers@freebsd.org" , FreeBSD Net , "Andrey V. Elsukov" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Sep 2013 03:20:11 -0000 On 13 September 2013 15:43, Rick Macklem 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. > Hi, the penalties to go to main memory quite a few times each time we process a frame is expensive. If we can get some better behaviour through batching leading to more efficient cache usage, it may not actually _have_ a delay. But, that requires a whole lot of design stars to align. And I'm still knee deep elsewhere, so I haven't really finished getting up to speed with what everyone else has done / said about it.. -adrian