From owner-freebsd-net@freebsd.org Mon Jun 26 16:26:22 2017 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 4D2BDD8B61C; Mon, 26 Jun 2017 16:26:22 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 C9BCB7F36C; Mon, 26 Jun 2017 16:26:21 +0000 (UTC) (envelope-from matt.joras@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id 77so147270960wrb.1; Mon, 26 Jun 2017 09:26:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L4JxaB/ZQ4GTAlGrgHDF4xJYCRU6c3BJAy3OSKIVAZg=; b=HtsofQLi2EZWMxV5XTjidUCq+khQLoNxqvR/s5+Rd2eDv52OwpTcIiAXIAGQJaZFfj RB+2a62ZmjlO+dhC6xnX0kVI39uhc+pY8xb96rhtCjdeKgF+NpKt/IIjDfxmWczY9O8N t1NcoEs0VEAjhu9+SlHJ6ma7WUjYVL6ctQTcZBAg/EMWYkcdKPA7lmKPuOUQWt3iKomQ JuqQSO8+9CwFLEw4FofSO3fQQiMb9hAdNa/tv7r8QDP9ZEQ4FpSrGhejQlmFDKBlZQeY FNoxUxT9TR+AlXlxNsJGSuBggDRN52rgw210xu4qIYRqDRZnFldsc1nrLsy6fUdjxjg9 EeaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L4JxaB/ZQ4GTAlGrgHDF4xJYCRU6c3BJAy3OSKIVAZg=; b=gyV+bTRhn3vCMkmxx1SFnx/IsJ/gJTOs+xxoRrCeYi+PFc7B4qhj5qZoUgQoRWhZn6 VG1Ol0yuabz/8wLCRCVneiNFvzK01sVPTT669YeGnw7YLQOiyfeMfaX2LpMdOFOdZP2F gw099Sf84FrsvJFw2qjUZrhrujOjkBTMWMqeTV5AMemfLqA90hwpLn3QlcZoApfP8QKE Fg/VZf6lF5aysk+9611VZzdDKlCM0Ad4/2Gjhg1jcpeVP5Telhy3Fi7vI+svDy93TNlC 3M2UR2NtoysE7ErFDv3K6i5HzztHIzFu3At8GEri/H/lG3e1V7vEOcB+wcNuMQJWM7w/ smlQ== X-Gm-Message-State: AKS2vOwqFFnI8Rr6f8H9ANmFvje4axFtFj9Oe5rj3kcvExJwhuQpbEkQ jv+D26Hpu8kg6o4wa3LargKofWqLDA== X-Received: by 10.223.160.40 with SMTP id k37mr13376113wrk.91.1498494380248; Mon, 26 Jun 2017 09:26:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.160.42 with HTTP; Mon, 26 Jun 2017 09:26:19 -0700 (PDT) In-Reply-To: <61f98b7d-f55d-aa0f-4aef-1bdfbc7086ff@yandex.ru> References: <486A6DA0-54C8-40DF-8437-F6E382DA01A8@gmail.com> <6a31ef00-5f7a-d36e-d5e6-0414e8b813c7@selasky.org> <613AFD8E-72B2-4E3F-9C70-1D1E43109B8A@gmail.com> <2c9a9c2652a74d8eb4b34f5a32c7ad5c@AM5PR0502MB2916.eurprd05.prod.outlook.com> <52A2608C-A57E-4E75-A952-F4776BA23CA4@gmail.com> <9B507AA6-40FE-4B8D-853F-2A9422A2DF67@gmail.com> <64abec26-e310-d66d-93ae-3536914ddd84@yandex.ru> <86D76532-92F4-479C-A714-126D007AD91F@gmail.com> <61f98b7d-f55d-aa0f-4aef-1bdfbc7086ff@yandex.ru> From: Matt Joras Date: Mon, 26 Jun 2017 09:26:19 -0700 Message-ID: Subject: Re: mbuf_jumbo_9k & iSCSI failing To: "Andrey V. Elsukov" Cc: Ben RUBSON , FreeBSD Net , Ryan Stone , "freebsd-scsi@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 26 Jun 2017 16:26:22 -0000 On Mon, Jun 26, 2017 at 6:36 AM, Andrey V. Elsukov wrote: > On 26.06.2017 16:29, Ben RUBSON wrote: >> >>> On 26 Jun 2017, at 15:25, Andrey V. Elsukov wrote: >>> >>> On 26.06.2017 16:27, Ben RUBSON wrote: >>>> >>>>> On 26 Jun 2017, at 15:13, Andrey V. Elsukov wrote: >>>>> >>>>> I think it is not mlxen specific problem, we have the same symptoms with >>>>> ixgbe(4) driver too. To avoid the problem we have patches that are >>>>> disable using of 9k mbufs, and instead only use 4k mbufs. >>>> >>>> Interesting feedback Andrey, thank you ! >>>> The problem may be then "general". >>>> So you still use large MTU (>=9000) but only allocating 4k mbufs, as a workaround ? >>> >>> Yes. >> >> Is it a kernel patch or a driver/ixgbe patch ? > > I attached it. > > -- > WBR, Andrey V. Elsukov I didn't think that ixgbe(4) still suffered from this problem, and we use it in the same situations rstone mentioned above. Indeed, ixgbe(4) doesn't presently suffer from this problem (you can see that in your patch, as it is only effectively changing the other drivers), though it used to. It looks like it was first fixed to not to in r280182.