From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Would you say this information window is well designed? Date: Tue, 23 Feb 2021 20:26:51 +0200 Message-ID: <83r1l6tzbo.fsf@gnu.org> References: <83eeh6vmg2.fsf@gnu.org> <835z2ivknw.fsf@gnu.org> <83sg5mu1hn.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2786"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org, stefankangas@gmail.com, drew.adams@oracle.com, dgutov@yandex.ru To: Peter Dean Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 23 19:28:59 2021 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 1lEcQc-0000b3-HA for ged-emacs-devel@m.gmane-mx.org; Tue, 23 Feb 2021 19:28:58 +0100 Original-Received: from localhost ([::1]:59172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lEcQb-0004IE-Jd for ged-emacs-devel@m.gmane-mx.org; Tue, 23 Feb 2021 13:28:57 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39066) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lEcOk-0001pP-C1 for emacs-devel@gnu.org; Tue, 23 Feb 2021 13:27:02 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49158) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lEcOj-0007u5-PB; Tue, 23 Feb 2021 13:27:01 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1469 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lEcOi-00068H-Er; Tue, 23 Feb 2021 13:27:01 -0500 In-Reply-To: (message from Peter Dean on Tue, 23 Feb 2021 17:59:08 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:265545 Archived-At: > Date: Tue, 23 Feb 2021 17:59:08 +0000 > From: Peter Dean > Cc: "drew.adams@oracle.com" , "stefankangas@gmail.com" , "larsi@gnus.org" , "dgutov@yandex.ru" , "emacs-devel@gnu.org" > > Then there could be a refresh rate value (e.g. 15 ms or some other value, > configurable) and thread-yield could check if the main thread got the lock > within this time window. > > If not then it would give the lock explicitly to the main thread, otherwise > the next thread gets the lock. thread-yield runs in the context of the thread that yields. You make it sound like there's some entity other than the involved threads which runs thread-yield, but that's not what happens. I really suggest to read the code, it is not too large and not hard to understand how it works. Then such discussions could be much more meaningful.