From owner-freebsd-fs@freebsd.org Wed Oct 31 20:02:39 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A88B10E848B; Wed, 31 Oct 2018 20:02:39 +0000 (UTC) (envelope-from avv314@gmail.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCE5E86C15; Wed, 31 Oct 2018 20:02:38 +0000 (UTC) (envelope-from avv314@gmail.com) Received: by mail-lf1-x133.google.com with SMTP id p17so6164919lfh.4; Wed, 31 Oct 2018 13:02:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m8Rgzg4293v3MVlEqea2Z8/+X11CqprUEMKGGxpMf7M=; b=rXmPAuR4J2WinO4QN0stdQXBuu2dw6s30eyTwy1rfW/s0AslJk3T/9PJWzjltTV/us eD21hKF6ddUsYfQJxPc4e2PjOoIuzzewSZKe1GRToUrtj5jqNKzE2/6NNvOJxfxTppsN 1J6QPbKPxuLMiT2r8moT20qfCsiwGx9OjhRaGsomhrpFWqdXcIXYbEuKylyPiT/8pkQh eE5CNS0DuXRKZ2b43bXr5y+GjYtnCo7HtndfTGeIUlxcyqhRePmp/z5AS+H/FKKz/lGD Uyi7MzMPZqfdlzJVbYuR03Szvo2aikkbQuuEvQE25s89pilOVSe2SpzKK34GgIyn6fjV qVaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m8Rgzg4293v3MVlEqea2Z8/+X11CqprUEMKGGxpMf7M=; b=PZHjdVA1FRZDKFyZS+GU9Cbco3DwHK7VvEgcB18HDcwANbVionT85CadCm5yusc92n i7ZYB52VusgPSYEi46jMbHL1+k5zobc8zMENUEPOAPjDCJA8iy9G2R31GU4iOxKDMzn4 00BBR+VW1CD53GOZk5nFbF8XclQPopxEKCOHQyU5Fr3wJLYC1qF/KOJrOQYTtMT3bMum 7vnDuGn1rP4Zlm/DZmy4Gy8uJv9epAHmcg/0ddWss6y/RcyC164uNu9KQ7JXtg835sGK 8ybjw8la3rpikFJDwTcV0xvzE1yJGpC43KXipw7UTEV+bI/ZHWaADM9yUpYgBlXClFOx Wlfg== X-Gm-Message-State: AGRZ1gJPg2ZoqQmv2ck2qTnQk4VenGZMEc7SWuK4ky5giHenNjAtve3p Z3KG1tM7WtfAaAb+REoOiq7/CfVwrzvcogm/8Ro= X-Google-Smtp-Source: AJdET5fK5/hXnhtK1kk37hm04GiVsSI8EQhhTYspjvmtsLFwkUBnpiq4vkNWHfgvcZVmtVINJJGcoNNBxt4QlosWLas= X-Received: by 2002:a19:6a13:: with SMTP id u19mr2700626lfu.46.1541016157376; Wed, 31 Oct 2018 13:02:37 -0700 (PDT) MIME-Version: 1.0 References: <201810291506.w9TF6YAP057202@pdx.rh.CN85.dnsmgr.net> In-Reply-To: From: Andrew Vylegzhanin Date: Wed, 31 Oct 2018 23:02:25 +0300 Message-ID: Subject: Re: NFS + Infiniband problem To: rmacklem@uoguelph.ca Cc: "Rodney W. Grimes" , freebsd-fs@freebsd.org, freebsd-infiniband@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 20:02:39 -0000 =D1=81=D1=80, 31 =D0=BE=D0=BA=D1=82. 2018 =D0=B3. =D0=B2 5:53, Rick Macklem= : > > > > >net.inet.tcp.cc.algorithm=3Dhtcp > Well, I'm not familiar with the current TCP stack (and, as noted before, I know > nothing about InfiniBand). All I can suggest is testing with the default congestion > control algorithm. (I always test with the default, which appears to be newreno.) > NFS traffic looks very different than a typical use of TCP. Lots of small TCP > segments in both directions interspersed with some larger ones (the write > requests or read replies). With this TCP settings same server serve NFS requests via 40G Ethernet on multiply clients with speed via 1G Eth ~ 105/110 MB/sec write/read. Of course I'll try to change congestion algorithm, but I don't think that will help. Also need to test setup with infniband set from connected mode to datagram mode. -- Andrew > > rick