Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1630283pxb; Thu, 4 Mar 2021 16:58:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJxbZ1Etved5bNulXYj8knPTQ6w4OMGkfN6ptboZfF4m+vNW/iBMV/Bp+EwQVIC+bvSF9OgC X-Received: by 2002:a92:8752:: with SMTP id d18mr5973800ilm.283.1614905883016; Thu, 04 Mar 2021 16:58:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614905883; cv=none; d=google.com; s=arc-20160816; b=BvE+OmV9adP8LqWM7XSWu4hzJlYZc4Tq/LSN4d+DtjUGqru6AfRnp9iicfo3ryoD+Q cztDfFrUHwT6YDZKY2aq5d92P0ljxjNCBJ1aXGT1/JvV2t8ZrFCZPCiqqI9y47Dbqqk9 uAgRWTU7pscnzMG2w1LYC8ZCer3SW/MEaAoZdDQXMkJfh7LmDBeLHJAluk/CUocRrarj 0DBuNRTJEugO7CFwVAGr2x9Ys8YCAv+XLIP4jk2I/s1Wwz72lVxxcKUPAGDGSIs26v3i q1JwdeKJQi6WFJ8gBTl0yXCp4VrXws1HKEYSUflOTpDyX9uKRsnQgwq+ShEKu5QgeIf5 11RA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=okpZzFCE+S/kjR2YiW6a2eXyNqNPc4VWZ1UoZTdt4R0=; b=ObZOWbSrzsCbB0+yuKZUXFu7FVlHJnCJbD14ijUZ2lvCHXwuEzUC9tiPIlmbA+rnnm ezRiR+rP+U5TBwET7WReZ6b4sohvicWsmC91Za/cxugotgQ87nSjfuhHimIZ3cejmEAd dT+ne0MeiFLr33zwNmQUuJGW77QhZEs3qOMe5zD1cN67mBqEcef08rJN6I9BeQRbckhp nXKLDzax+G2Uk4uWdmGdoT+dskAm4mUqWOsAv4q0tTKNOmZJHlUWg4GpVEozGH2JSyzw nfk74sX2+qzAWGqAQLYHW80H2ETofdEtB0AAJCmXA/xEJ9sGKtHoRRuMuc3FLvFw9dus L4IQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=euDRZRTe; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=zKrAHtGA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z10si876529ior.84.2021.03.04.16.57.49; Thu, 04 Mar 2021 16:58:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=euDRZRTe; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=zKrAHtGA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236643AbhCDU7F (ORCPT + 99 others); Thu, 4 Mar 2021 15:59:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236210AbhCDU67 (ORCPT ); Thu, 4 Mar 2021 15:58:59 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B4BA9C061574 for ; Thu, 4 Mar 2021 12:58:19 -0800 (PST) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1614891498; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=okpZzFCE+S/kjR2YiW6a2eXyNqNPc4VWZ1UoZTdt4R0=; b=euDRZRTeUVy0kkR2YRYIz8iu3IYbbMcaRDR7Fw0721nXYFm6ZH0QHJRyc7ksYZQIbuN0Vl NXs2UiiLx6p99lTTjd04Ss/YGagIPE+rByGqpUDHQBNRJNKqh7asfr8fbsbxTCovV2CyzX aF6PL1S74HIxampQ2tqbdSgcaaBOWOt+vsUeB6vHxGvz/F/fRNjkUeDRn0mBzNmpn/jG4w Jbp1jWzuanSBkavga1QU8TckKmekOUa7/GChmD64yFV2+N8S0ZAQJnQ8J8zgaP+89SNWws ffizAqVy2N6Ml3ubX2oJwgKXoiR0aZSvUW+hsJdyC+7rq0zciT+38YbdEzYw2A== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1614891498; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=okpZzFCE+S/kjR2YiW6a2eXyNqNPc4VWZ1UoZTdt4R0=; b=zKrAHtGAZ+33kwzte2cezMBQ5pox4xJC9EqlZyyqRztMcSOw54Sc8E80MZOEArz0jtEkQP vkHFdD0YjmSYFEBA== To: "Eric W. Biederman" Cc: Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Oleg Nesterov , Matt Fleming Subject: Re: [PATCH] signal: Allow RT tasks to cache one sigqueue struct In-Reply-To: References: <20210303142025.wbbt2nnr6dtgwjfi@linutronix.de> <20210304081142.digtkddajkadwwq5@linutronix.de> <87tupr55ea.fsf@nanos.tec.linutronix.de> Date: Thu, 04 Mar 2021 21:58:17 +0100 Message-ID: <87lfb263h2.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 04 2021 at 13:04, Eric W. Biederman wrote: > Thomas Gleixner writes: >> >> We could of course do the caching unconditionally for all tasks. > > Is there any advantage to only doing this for realtime tasks? It was mostly to avoid tons of cached entries hanging around all over the place. So I limited it to the case which the RT users deeply cared about. Also related to the accounting question below. > If not it probably makes sense to do the caching for all tasks. > > I am wondering if we want to count the cached sigqueue structure to the > users rt signal rlimit? That makes some sense, but that's a user visible change as a single signal will up the count for a tasks lifetime while today it is removed from accounting again once the signal is delivered. So that needs some thought. Thanks, tglx