From owner-freebsd-current@freebsd.org Thu Jun 8 21:19:17 2017 Return-Path: Delivered-To: freebsd-current@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 3E776C79D4E for ; Thu, 8 Jun 2017 21:19:17 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 BE28A71ECE for ; Thu, 8 Jun 2017 21:19:16 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id q97so23324665wrb.2 for ; Thu, 08 Jun 2017 14:19:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=1JXlnHMr5d3XS9tQ+1QvWKhedk6feNcTcWQakoQQPr4=; b=sq67puKZkmEI778lvt1Xy91RoLT1nsZrhIXn6NCN+boHMMj2t/wvF2XZ4kB6ldbk2+ 2ohzEevpimSMqPmx9Ni4+NQegtUNCftYm+dVkEFsJZA/lazM3wpqZgyBFSmFHfddTWvM NyHGK11G45RWQRPMBXioMlw1aKv5lTugypeUPw6mBC5RbBUWsTQqUpJuX7kkpW+Wcq24 s2j3G6eehTvCWJyxDxZ95H5B9Ctrt1nTUZgb3FqEGl8RtyUCoGNqdak4gcpX8nJFS9hc +qQFxwiHIkdwYAFW5rCg2lxPVsMqr2KMFnXzoXvT5N/5fykZHx5g0xeGEf4tcxly1CVk ISNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=1JXlnHMr5d3XS9tQ+1QvWKhedk6feNcTcWQakoQQPr4=; b=qn7tGVg0KGbwG6lnMRBHwdx3K60NQf6Fpl2jBDobgiJNA7NcjWMeY/zKJtoRGs90KC 4mi0891PR43sfVkKCx65RwAhjqnAzun9gk0rHPmImubOYPesygMVVmNXcTl+DC1G+t2n lJFmT4vLUNAdXT5ZRfYKfDKP36lkWWTj44IhDNHwCaZ61l2K+vkgzxTUkU/Vz/dzFc2+ AY7I0DpfW7whuylIU0TJe7xB4+E46Z0t1q+4nAr1ZOKIm3GNxNeGwIPUcmQLTyA3CHXo FSauVwUHUm9spIDnkw+URQ5UbdrLa9KmhS17feK4UqFYD/z1CspMS9XOTlHwIFlPJwYZ b93w== X-Gm-Message-State: AODbwcCVuSrKe3/RsO0gKI+EZELUea84uHHL7afMWv94alCmju0LIWAi p3v6+kr9xWoztQ== X-Received: by 10.223.135.78 with SMTP id 14mr26790560wrz.166.1496956755215; Thu, 08 Jun 2017 14:19:15 -0700 (PDT) Received: from brick (cpc92310-cmbg19-2-0-cust934.5-4.cable.virginm.net. [82.9.227.167]) by smtp.gmail.com with ESMTPSA id 64sm8482246wmn.20.2017.06.08.14.19.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 14:19:14 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Thu, 8 Jun 2017 22:19:11 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: peter.blok@bsd4all.org Cc: Hans Petter Selasky , Tomoaki AOKI , freebsd-current@freebsd.org Subject: Re: Time to increase MAXPHYS? Message-ID: <20170608211911.GB5348@brick> Mail-Followup-To: peter.blok@bsd4all.org, Hans Petter Selasky , Tomoaki AOKI , freebsd-current@freebsd.org References: <0100015c6fc1167c-6e139920-60d9-4ce3-9f59-15520276aebb-000000@email.amazonses.com> <972dbd34-b5b3-c363-721e-c6e48806e2cd@elischer.org> <3719c729-9434-3121-cf52-393a4453d0b2@freebsd.org> <20170604163948.eb5f74ce2a233b8f204ba671@dec.sakura.ne.jp> <15e42fd1-055d-28f6-5e24-1448e16954a9@selasky.org> <20170605174930.GA6259@brick> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2017 21:19:17 -0000 Huh, can't say I've tested that. I'll try to look into this. Thanks for the report! On 0608T2046, peter.blok@bsd4all.org wrote: > One area that breaks after changing MAXPHYS from 128K to 1MB is the iscsi target. I don’t have details, because that server is semi-production and I reverted it back ASAP > > On 5 Jun 2017, at 19:49, Edward Tomasz Napierała wrote: > > > > On 0604T0952, Hans Petter Selasky wrote: > >> On 06/04/17 09:39, Tomoaki AOKI wrote: > >>> Hi > >>> > >>> One possibility would be to make it MD build-time OTIONS, > >>> defaulting 1M on regular systems and 128k on smaller systems. > >>> > >>> Of course I guess making it a tunable (or sysctl) would be best, > >>> though. > >>> > >> > >> Hi, > >> > >> A tunable sysctl would be fine, but beware that commonly used firmware > >> out there produced in the millions might hang in a non-recoverable way > >> if you exceed their "internal limits". Conditionally lowering this > >> definition is fine, but increasing it needs to be carefully verified. > >> > >> For example many USB devices are only tested with OS'es like Windows and > >> MacOS and if these have any kind of limitation on the SCSI transfer > >> sizes, it is very likely many devices out there do not support any > >> larger transfer sizes either. > > > > FWIW, when testing cfiscsi(4) with Windows and OSX I've noticed > > that both issue 1MB requests. I wouldn't be surprised if they avoided > > doing that for older devices, depending on eg the SCSI version reported > > by device. > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org " >