From owner-freebsd-arm@freebsd.org  Sat Mar  3 16:26:10 2018
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@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 E0A4AF2569F
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Sat,  3 Mar 2018 16:26:10 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (www.zefox.net [69.239.235.194])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 5D09268A33
 for <freebsd-arm@freebsd.org>; Sat,  3 Mar 2018 16:26:10 +0000 (UTC)
 (envelope-from fbsd@www.zefox.net)
Received: from www.zefox.net (localhost [127.0.0.1])
 by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w23GQ6VI042019
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 3 Mar 2018 08:26:07 -0800 (PST)
 (envelope-from fbsd@www.zefox.net)
Received: (from fbsd@localhost)
 by www.zefox.net (8.15.2/8.15.2/Submit) id w23GQ5UT042018;
 Sat, 3 Mar 2018 08:26:05 -0800 (PST) (envelope-from fbsd)
Date: Sat, 3 Mar 2018 08:26:05 -0800
From: bob prohaska <fbsd@www.zefox.net>
To: Warner Losh <imp@bsdimp.com>
Cc: Mike <the.lists@mgm51.com>,
 "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>,
 bob prohaska <fbsd@www.zefox.net>
Subject: Re: Is maximum swap usage tunable?
Message-ID: <20180303162605.GA41874@www.zefox.net>
References: <20180228170311.GA26187@www.zefox.net>
 <a759ecea-83f4-b0b2-7113-c39633f68637@mgm51.com>
 <20180228185517.GB26187@www.zefox.net>
 <8f422161-885e-aa91-eacd-018540222d65@mgm51.com>
 <20180228214301.GA29481@www.zefox.net>
 <b82801b8-bc29-414c-1170-621bb4a5d937@mgm51.com>
 <CANCZdfq_MpxjUyVd-=+MiAQAER4TeDh9irhx_evdXwa3yt3h0g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANCZdfq_MpxjUyVd-=+MiAQAER4TeDh9irhx_evdXwa3yt3h0g@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 16:26:11 -0000

On Fri, Mar 02, 2018 at 10:04:56AM -0700, Warner Losh wrote:
> On Fri, Mar 2, 2018 at 9:19 AM, Mike <the.lists@mgm51.com> wrote:
> 
> >
> > buildworld is still running.  I started it around 3PM (EST) on March 1.
> >
> > I'm seeing a lot of swap messages on the console.  The text is:
> >
> >   swap_pager: indefinite wait buffer: bufobj: 0,
> >      blkno: [varies], size: [varies]
> 
> 
> This message comes from the swap pager when the I/O doesn't complete
> quickly enough. It has nothing to do with sizes of the swap space.
> 
> I've seen three causes for this: (1) The driver going crazy and not
> completing I/Os it gets notified as being done; (2) The driver not having a
> backstop timer on I/Os to fail them with timeout; (3) timeouts not firing
> for the driver to fail the I/O up the stack. (4) when a drive suddenly slow
> way way down (~100x or more slower), the I/O queues balloons and you can
> get these.
> 

Is there some sort of experiment which can distinguish hardware delays
from software delays? For example, would logging gstat output shed any
light? 

Thanks for reading,

bob prohaska