From owner-freebsd-scsi@freebsd.org Mon Jun 26 16:33:04 2017 Return-Path: Delivered-To: freebsd-scsi@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 52531D8B9C3; Mon, 26 Jun 2017 16:33:04 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3j.cmail.yandex.net (forward3j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB2E67F964; Mon, 26 Jun 2017 16:33:03 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [95.108.130.59]) by forward3j.cmail.yandex.net (Yandex) with ESMTP id 19E3D20DAE; Mon, 26 Jun 2017 19:33:00 +0300 (MSK) Received: from smtp1j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1j.mail.yandex.net (Yandex) with ESMTP id 47C8D3C80F56; Mon, 26 Jun 2017 19:32:56 +0300 (MSK) Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id AJ1ygWDziH-WuoiBls4; Mon, 26 Jun 2017 19:32:56 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1498494776; bh=+Nkw5KkQClkY3jfyBfJ8TMZbKDMZn/Ap1JQPuiUgof0=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=OOlT2o9BXjq0Bv4mtClYdLxHN0hLJ/LIPB1B3P4JQKGQ0M+8Vk/FRpvr+OEZo7RjV HfTF8wCe2bi0MjLU6M6C6UzQQ1Er96sxe7B1sJeKpRrxm8A6CU2a2FueRqpmcuB5KP Gogqsr7z04ah5SMW5cn6lR8PDJGyGQCYVKBcdQsI= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: mbuf_jumbo_9k & iSCSI failing To: Matt Joras Cc: Ben RUBSON , FreeBSD Net , Ryan Stone , "freebsd-scsi@freebsd.org" 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: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Mon, 26 Jun 2017 19:30:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LSl5TAswqMcmo5tKJaEuQNEMULCLPXSuI" X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 16:33:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LSl5TAswqMcmo5tKJaEuQNEMULCLPXSuI Content-Type: multipart/mixed; boundary="W5Mi1AjedTkUXLfJKKc2QlKE0GnXDnkwL"; protected-headers="v1" From: "Andrey V. Elsukov" To: Matt Joras Cc: Ben RUBSON , FreeBSD Net , Ryan Stone , "freebsd-scsi@freebsd.org" Message-ID: Subject: Re: mbuf_jumbo_9k & iSCSI failing 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> In-Reply-To: --W5Mi1AjedTkUXLfJKKc2QlKE0GnXDnkwL Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 26.06.2017 19:26, Matt Joras wrote: > 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. >=20 Yes, actually we have this patch since 8.x. Recent drivers aren't affected by this problem. iflib also has the code: #ifndef CONTIGMALLOC_WORKS else fl->ifl_buf_size =3D MJUMPAGESIZE; #else else if (sctx->isc_max_frame_size <=3D 4096) fl->ifl_buf_size =3D MJUMPAGESIZE; else if (sctx->isc_max_frame_size <=3D 9216) fl->ifl_buf_size =3D MJUM9BYTES; else fl->ifl_buf_size =3D MJUM16BYTES; #endif that seems by default doesn't use 9-16k mbufs. --=20 WBR, Andrey V. Elsukov --W5Mi1AjedTkUXLfJKKc2QlKE0GnXDnkwL-- --LSl5TAswqMcmo5tKJaEuQNEMULCLPXSuI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAllRNp4ACgkQAcXqBBDI oXqBbwgAq7tK/6KFBl04+UzquamnCs4v85dAx65EG8gHFVAXkOSYW9rXBSieX2wU 9JPZNQmDF9eO6xv4oFHQg87bwIs6WEWKc3TO1iR+7mDycRDi/7dEEzmyi1Px4HFx 8gAnaF6VqTjixRfPRuXQ8eZXR6mKFGSVdiHwFrqZ6M6DTEZiqCxjAa7ZfF6mFSwH cs44QmzYCGP+bI6PIwF4ylI7gVgD7yWg/3zWxO0J5i3T+65+ZKAd4gznb09HxzHB R7mmoYWOsm/V9g07MlLhHkRzD9+Ozhm/dJk8F1WgP6gXvxh7etJHGuY9W7xl5Ic9 9MpgQB9xUoKrtqWPSHAX+pbx3tP94w== =Al7R -----END PGP SIGNATURE----- --LSl5TAswqMcmo5tKJaEuQNEMULCLPXSuI--