From owner-svn-src-all@freebsd.org Fri Sep 7 15:52:32 2018 Return-Path: Delivered-To: svn-src-all@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 B2DDFFFE468; Fri, 7 Sep 2018 15:52:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBC6C8EA1F; Fri, 7 Sep 2018 15:52:31 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf1-x432.google.com with SMTP id j8-v6so7220029pff.6; Fri, 07 Sep 2018 08:52:31 -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:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DUggq7dELOtCB5Jdr44+73kgvTHUNyIZ+3kIuenALOU=; b=Idm4M/JQR6d3hFUwNwQj0+hVoDJctfS82ob7O1amreNv1jgo7jQyFVtWzQeqTjjbdP VOkKF1b2oS0lg7kj2PuUuT3/8ekSZJ02rcK6uu/Fkb7uikpHR8KEZClAA7zzRxUCTnp9 /Df4NpGN34YfBvQy/Ogsa5hU8tznMusxUm3i5NtjH/aI+GjSDdcqUQ+SNfNw0vAE8htK YiiO/vLd1Z90sMI0jSPxksFZhR5lFecrYbSxWEW8JEk3gOmuhxteMYMMzN1BMjs6aEKG txmhh4F8uTVQgU5G4AkMv++kuMpaiWV4J3405PC/8Mb+8E9xzed+vE16Dp4JyK3er0qw XSpw== 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 :references:mime-version:content-disposition:in-reply-to:user-agent; bh=DUggq7dELOtCB5Jdr44+73kgvTHUNyIZ+3kIuenALOU=; b=txb7V5U/V99YZT30B1muvrmtlde/MMFIzkLKe+tcVhU4nR7mAvy9uTGQIF4c9BL728 4oeQhFntKp3xHTFWhosJVhOHQdiB9vs3gjnX0az/hnj0347RaFWWUFNj5hGRCjW+qpEB ug3SUYukXZwJkD/Pf80cvbACrmvG+ZrXIe61NkqT6QOVINwprWGPv6uFAZbJVGutu02F CT+Mj4ppoqpdyAiH++qe1FnUgVAY/8IA77an5jc9VoX9h77j+JwcPT1gDPVFmZap13l7 LEQODVKdQwfpKQjZ0ZBd863OGWORoDEf7t1nvUovCqI7Mik92biLBdrnVgNlaRg69LAV urQA== X-Gm-Message-State: APzg51B4e21Igq2KEJ3CHzoEqzXnWG1YOWYj8KtDQdLsS9eUxxx9oah9 6ek5nP19SbDZk0PdaZeN4vbi0Lkl X-Google-Smtp-Source: ANB0VdaNJ7PHRY+BkawTnr08HN1Z39+57X49xxLx0l4WZpMF0fzYtqAOFoWfcW0yMOeqCRNlun6m5A== X-Received: by 2002:a62:9bc9:: with SMTP id e70-v6mr9018464pfk.95.1536335550509; Fri, 07 Sep 2018 08:52:30 -0700 (PDT) Received: from raichu (toroon0560w-lp130-09-70-52-224-239.dsl.bell.ca. [70.52.224.239]) by smtp.gmail.com with ESMTPSA id g25-v6sm16850043pfd.23.2018.09.07.08.52.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Sep 2018 08:52:29 -0700 (PDT) Sender: Mark Johnston Date: Fri, 7 Sep 2018 11:52:24 -0400 From: Mark Johnston To: Alexander Leidinger Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r338507 - in head/sys: sys vm Message-ID: <20180907155224.GA63224@raichu> References: <201809061928.w86JSrSb067799@repo.freebsd.org> <20180907095010.Horde.LHANrMIgb7RjrRNYbtaBqYT@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180907095010.Horde.LHANrMIgb7RjrRNYbtaBqYT@webmail.leidinger.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2018 15:52:32 -0000 On Fri, Sep 07, 2018 at 09:50:10AM +0200, Alexander Leidinger wrote: > Quoting Mark Johnston (from Thu, 6 Sep 2018 > 19:28:53 +0000 (UTC)): > > > Author: markj > > Date: Thu Sep 6 19:28:52 2018 > > New Revision: 338507 > > URL: https://svnweb.freebsd.org/changeset/base/338507 > > > > Log: > > Avoid resource deadlocks when one domain has exhausted its memory. Attempt > > other allowed domains if the requested domain is below the minimum paging > > threshold. Block in fork only if all domains available to the forking > > thread are below the severe threshold rather than any. > > Could the problem you fixed manifest itself in e.g. a hanging system > due to not enough memory free despite top displaying a lot of memory > free (let's assume 2 memory domains and several gigs in both)? Yes. > I have a system which never went below a specific amount of memory > (before the fix of the no-rebalancing bug in the scheduler) if NUMA > was enabled. With NUMA disabled I see much less memory free. I haven't > tried NUMA after the fix of the scheduler, but would give it a try > again if you think this could be a manifestation of the problem. I think it's worth trying again.