From debbugs-submit-bounces@debbugs.gnu.org Sun May 24 10:27:15 2020 Received: (at submit) by debbugs.gnu.org; 24 May 2020 14:27:15 +0000 Received: from localhost ([127.0.0.1]:38421 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcras-0007ov-Nq for submit@debbugs.gnu.org; Sun, 24 May 2020 10:27:14 -0400 Received: from lists.gnu.org ([209.51.188.17]:48826) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jcrao-0007ol-GO for submit@debbugs.gnu.org; Sun, 24 May 2020 10:27:14 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43826) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jcrao-0006J2-B0 for guix-patches@gnu.org; Sun, 24 May 2020 10:27:10 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:60908) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcran-0006xA-GR; Sun, 24 May 2020 10:27:09 -0400 Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=54098 helo=gnu.org) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jcral-00015z-GI; Sun, 24 May 2020 10:27:08 -0400 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= To: guix-patches@gnu.org Subject: [PATCH Shepherd 0/2] Use 'signalfd' on GNU/Linux Date: Sun, 24 May 2020 16:27:00 +0200 Message-Id: <20200524142700.6151-1-ludo@gnu.org> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: submit Cc: =?UTF-8?q?Ludovic=20Court=C3=A8s?= X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Hello! This patch series allows shepherd to use ‘signalfd’ on GNU/Linux. It allows us to avoid race conditions related to signal delivery, which in turn means we can pass an infinite timeout to ‘select’, and thus increase battery life. More generally, it’s a way to structure the code around the event loop. The next step will be to make the code entirely reactive, so we can have things like socket activation, being able to start services that don’t depend on one another concurrently, and all that. (This is actually also be possible without ‘signalfd’ but it’s more consistent and robust to have everything visible to ‘select’.) Thoughts? I guess the main question is: can it go into 0.8.1, which we outta release soon due to . I’d say “yes”, but I’ll be even more confident if others take a look. :-) Ludo’. Ludovic Courtès (2): system: Add support for 'signalfd'. shepherd: Use 'signalfd' when possible. configure.ac | 18 +++++++++ modules/shepherd.scm | 73 ++++++++++++++++++++++++++++++---- modules/shepherd/service.scm | 19 +++++---- modules/shepherd/system.scm.in | 65 ++++++++++++++++++++++++++++++ 4 files changed, 161 insertions(+), 14 deletions(-) -- 2.26.2