From owner-freebsd-net@FreeBSD.ORG Tue Jan 28 06:28:44 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 C96C9B14; Tue, 28 Jan 2014 06:28:44 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DC941C9A; Tue, 28 Jan 2014 06:28:44 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id x13so7121234ief.37 for ; Mon, 27 Jan 2014 22:28:42 -0800 (PST) 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=MIYIa4w/O3tQmMg88kcxETTAMgoN0ggwnVRCLgpfLfk=; b=QkYKol6EZhtDNhAWdiAL+dfYPeurYjjSDdyIza32q1N6oobbrzBH2jpHm0vZEsVbo+ siYsVuPa45xQv+HzopCFgKthF5//1PvAASBzc21Oy9ZM7ZxbyBjnCuo81K0hfhTA5c6W G7Pe06UcA88V0Xh1Ci0G6eRj+2HCkO2p9/OIX7stGwvAIql5mI8qeiL9W2Z5fjRKG8TN Ik00GfTKdib6dtt6Zc1DO4JSpDUZW83PueTIw/oYbbvb7Jncl3z+jx5jgDbeYFOTrM3t GoUyXqhcJ4OmnuOZcbWes7hw+zjjDX6sqtIpCJUzgSpWMgW8HSCG1lvIUMgzH76BDoVG e+Ew== MIME-Version: 1.0 X-Received: by 10.50.13.9 with SMTP id d9mr21433238igc.25.1390890522907; Mon, 27 Jan 2014 22:28:42 -0800 (PST) Sender: jdavidlists@gmail.com Received: by 10.42.170.8 with HTTP; Mon, 27 Jan 2014 22:28:42 -0800 (PST) In-Reply-To: <201401280427.s0S4RTVn077761@hergotha.csail.mit.edu> References: <20140128002826.GU13704@funkthat.com> <1415339672.17282775.1390872779067.JavaMail.root@uoguelph.ca> <201401280427.s0S4RTVn077761@hergotha.csail.mit.edu> Date: Tue, 28 Jan 2014 01:28:42 -0500 X-Google-Sender-Auth: mRtwRKtE_tp1KE4p2pUa9Xn1F4I Message-ID: Subject: Re: Terrible NFS performance under 9.2-RELEASE? From: J David To: wollman@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Rick Macklem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 06:28:44 -0000 A few questions as I try to parse the various patches floating around for this. What's the difference between src/sys/nfsserver and src/sys/fs/nfsserver? It looks like maybe the former is for NFSv3 and the latter is for NFSv4? If so, these patches appear to be for the NFSv4 server. Since we are using the NFSv3 server exclusively, does that mean we would need to do something similar somewhere in the neighborhood of line 930 of src/sys/nfsserver/nfs_serv.c? Also, these patches appear server-side. To make sure things flow smoothly, will additional client-side changes be necessary? There is some MGET/MCLGET in src/sys/nfsclient/nfs_subs.c. (The equivalent in src/sys/fs/nfsclient/nfs_clcomsubs.c appear to be using the NFSMGET/NFSMCLGET macros, so presumably those are handled?) In any case, the switch from 2k to 4k mbufs and m_getm2 seems well worthwhile regardless of whether it addresses this specific issue. It should reduce a lot of overhead in many common cases. If my understanding isn't too far off, I can take a whack at testing the result, but only on NFSv3. Thanks!