From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: master 5c532fe303: Recommend that the user turn off memory overcommit Date: Sat, 09 Apr 2022 12:27:20 +0200 Organization: Linux Private Site Message-ID: <87ilria6wn.fsf@Rainer.invalid> References: <164941780605.21656.13343783431945268284@vcs2.savannah.gnu.org> <20220408113647.815ACC051D6@vcs2.savannah.gnu.org> <87wnfyoc8l.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10473"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:JuNaadMlh1UAtromt6TwGKjV4Fs= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 09 12:28:37 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nd8Kb-0002Xb-Pw for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Apr 2022 12:28:37 +0200 Original-Received: from localhost ([::1]:45228 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nd8Ka-0008DE-9y for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Apr 2022 06:28:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34420) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nd8Ja-0007WT-MH for emacs-devel@gnu.org; Sat, 09 Apr 2022 06:27:34 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:54414) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nd8JX-000625-Nz for emacs-devel@gnu.org; Sat, 09 Apr 2022 06:27:34 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nd8JT-0001Do-Jb for emacs-devel@gnu.org; Sat, 09 Apr 2022 12:27:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:288014 Archived-At: Po Lu writes: > Phil Sainty writes: >> I keep seeing the choice of process to kill being described as >> "random", but it is not random. > > It is random, from the perspective of the user, who eventually develops > the sinking feeling that the kernel might not kill IceCat but Emacs the > next time it happens. Random means different things to different people in various languages and contexts. From the user perspective I think I would describe the behaviour of the OOM killer as "unpredictable". As Phil said, if you had the same information the kernel uses, the user could in principle know what process it is going to select, however that data usually is not available to the user when the OOM killer triggers. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada