From owner-freebsd-net@freebsd.org Mon Jun 29 16:33:33 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B11B198FF23 for ; Mon, 29 Jun 2015 16:33:33 +0000 (UTC) (envelope-from stl@wiredrive.com) Received: from mail-wg0-f69.google.com (mail-wg0-f69.google.com [74.125.82.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4156F243D for ; Mon, 29 Jun 2015 16:33:32 +0000 (UTC) (envelope-from stl@wiredrive.com) Received: by wgfk9 with SMTP id k9so1070456wgf.1 for ; Mon, 29 Jun 2015 09:33:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uZ5vODSfKw+OU1dcSbQ9sZq0jIPqwkZS+y/4Y19uVFU=; b=AXq01zGQEEN+afwDEPar4d6RVl2kwpu0aNM0cQSnZZI/IZtbMUOMtnwyE8DZOneqCt 3ir9Hq8FzTROHHZWvaNHtAkdcA0Ue/Zzyq1l60OBh5taNmgdwNdpeKv8wzmru1KRHuFG LRZrlEol2URwQXuTaPbsqIGT+nxzoZAvVC/qAPmV94dumm7DnD/+5Bve+5ym2Cl8oxEy 3h6mXzsDBnGxTiwuRJ/pq0DfYA4jwUNZZkjihwPk0xhCr8pl/8CTyL1OCf8CmZ/SPJHe 2HgkNWKFWrdsuPocFN5xU6T88A9HJXbFiE2qiL7afxCejYgwVUSvY4KWUSQjDPj7WmwN NopQ== X-Gm-Message-State: ALoCoQkJLJjQEXIUupGNWpsf3TqySGhGqQbNSG017Zw/0Awz9Wj6nDV5E+KucpYkmBmi3NxSosPk MIME-Version: 1.0 X-Received: by 10.152.179.234 with SMTP id dj10mr15064875lac.73.1435595604795; Mon, 29 Jun 2015 09:33:24 -0700 (PDT) Received: by 10.25.156.208 with HTTP; Mon, 29 Jun 2015 09:33:24 -0700 (PDT) In-Reply-To: <1542755683.900028.1435580547450.JavaMail.zimbra@uoguelph.ca> References: <20150625145238.12cf9da3b368ef0b9a30f193@aei.mpg.de> <1629011632.413406.1435365728977.JavaMail.zimbra@uoguelph.ca> <20150629091958.af9720d478a8903ab28adc1d@aei.mpg.de> <1542755683.900028.1435580547450.JavaMail.zimbra@uoguelph.ca> Date: Mon, 29 Jun 2015 09:33:24 -0700 Message-ID: Subject: Re: NFS on 10G interface terribly slow From: Scott Larson To: Rick Macklem Cc: =?UTF-8?B?R2Vycml0IEvDvGhu?= , freebsd-net@freebsd.org, carsten aulbert Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2015 16:33:33 -0000 82599 in our case. One problem I do have is the stack likes to blow up on occasion with the right combo of high load and high throughput while TSO is enabled, possibly relating to the 10.x driver issue you've pointed out. But when it comes to the throughput they'll blast 10G with no problem. *[image: userimage]Scott Larson[image: los angeles] Lead Systems Administrator[image: wdlogo] [image: linkedin] [image: facebook] [image: twitter] [image: instagram] T 310 823 8238 x1106 <310%20823%208238%20x1106> | M 310 904 8818 <310%20904%208818>* On Mon, Jun 29, 2015 at 5:22 AM, Rick Macklem wrote: > Gerrit Kuhn wrote: > > On Fri, 26 Jun 2015 20:42:08 -0400 (EDT) Rick Macklem > > wrote about Re: NFS on 10G interface terribly > slow: > > > > RM> Btw, can you tell us what Intel chip(s) you're using? > > > > I have > > > > ix0@pci0:5:0:0: class=0x020000 card=0x00028086 chip=0x15288086 rev=0x01 > > hdr=0x00 vendor = 'Intel Corporation' > > device = 'Ethernet Controller 10-Gigabit X540-AT2' > > class = network > > subclass = ethernet > > > Yea, I don't know how to decode this either. I was actually interested in > what chip Scott was using and getting wire speed. > As noted in the other reply, since disabling TSO didn't help, you probably > aren't affected by this issue. > > rick > > > RM> For example, from the "ix" driver: > > RM> #define IXGBE_82598_SCATTER 100 > > RM> #define IXGBE_82599_SCATTER 32 > > > > Hm, I cannot find out into which chipset number this translates for my > > device... > > > > RM> Btw, it appears that the driver in head/current now sets > > RM> if_hw_tsomaxsegcount, but the driver in stable/10 does not. This > means > > RM> that the 82599 chip will end up doing the m_defrag() calls for 10.x. > > > > So the next step could even be updating to -current... > > OTOH, I get the same (bad) resulsts, no matter if TSO is enabled or > > disabled on the interface. > > > > > > cu > > Gerrit > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > >