From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DA840C4320E for ; Fri, 27 Aug 2021 17:04:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B62F661002 for ; Fri, 27 Aug 2021 17:04:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233613AbhH0REw (ORCPT ); Fri, 27 Aug 2021 13:04:52 -0400 Received: from out30-132.freemail.mail.aliyun.com ([115.124.30.132]:39023 "EHLO out30-132.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233392AbhH0REv (ORCPT ); Fri, 27 Aug 2021 13:04:51 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R221e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04395;MF=haoxu@linux.alibaba.com;NM=1;PH=DS;RN=8;SR=0;TI=SMTPD_---0UmHyjUW_1630083839; Received: from 192.168.31.215(mailfrom:haoxu@linux.alibaba.com fp:SMTPD_---0UmHyjUW_1630083839) by smtp.aliyun-inc.com(127.0.0.1); Sat, 28 Aug 2021 01:03:59 +0800 Subject: Re: [PATCH for-5.15 v2] io_uring: consider cgroup setting when binding sqpoll cpu From: Hao Xu To: Jens Axboe , Zefan Li , Tejun Heo , Johannes Weiner , Pavel Begunkov Cc: io-uring@vger.kernel.org, cgroups@vger.kernel.org, Joseph Qi References: <20210827141315.235974-1-haoxu@linux.alibaba.com> <0988b0dc-232f-80cd-c984-2364c0dee69f@kernel.dk> <592ba01a-a128-f781-d920-2b480f91c451@linux.alibaba.com> Message-ID: Date: Sat, 28 Aug 2021 01:03:59 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: <592ba01a-a128-f781-d920-2b480f91c451@linux.alibaba.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org 在 2021/8/28 上午12:57, Hao Xu 写道: > 在 2021/8/27 下午10:18, Jens Axboe 写道: >> On 8/27/21 8:13 AM, Hao Xu wrote: >>> Since sqthread is userspace like thread now, it should respect cgroup >>> setting, thus we should consider current allowed cpuset when doing >>> cpu binding for sqthread. >> >> In general, this looks way better than v1. Just a few minor comments >> below. >> >>> @@ -7000,6 +7001,16 @@ static bool io_sqd_handle_event(struct >>> io_sq_data *sqd) >>>       return did_sig || test_bit(IO_SQ_THREAD_SHOULD_STOP, &sqd->state); >>>   } >>> +static int io_sq_bind_cpu(int cpu) >>> +{ >>> +    if (!test_cpu_in_current_cpuset(cpu)) >>> +        pr_warn("sqthread %d: bound cpu not allowed\n", current->pid); >>> +    else >>> +        set_cpus_allowed_ptr(current, cpumask_of(cpu)); >>> + >>> +    return 0; >>> +} >> >> This should not be triggerable, unless the set changes between creation >> and the thread being created. Hence maybe the warn is fine. I'd probably >> prefer terminating the thread at that point, which would result in an >> -EOWNERDEAD return when someone attempts to wake the thread. >> >> Which is probably OK, as we really should not hit this path. > Actually I think cpuset change offen happen in container environment( > at leaset in my practice), eg. by resource monitor and balancer. So I > did this check to make sure we are still maintain sq_cpu logic at that > time as possible as we can. Though the problem is still there during > sqthread running time(the cpuset can change at anytime, which changes > the cpumask of sqthread) And because the cpumask of sqthread may be changed by the cgroup cpuset change at any time, so here I just print a warnning rather than terminating sqthread due to this 'normal thing'.. > > Regards, > Hao >> >>> diff --git a/include/linux/cpuset.h b/include/linux/cpuset.h >>> index 04c20de66afc..fad77c91bc1f 100644 >>> --- a/include/linux/cpuset.h >>> +++ b/include/linux/cpuset.h >>> @@ -116,6 +116,8 @@ static inline int cpuset_do_slab_mem_spread(void) >>>   extern bool current_cpuset_is_being_rebound(void); >>> +extern bool test_cpu_in_current_cpuset(int cpu); >>> + >>>   extern void rebuild_sched_domains(void); >>>   extern void cpuset_print_current_mems_allowed(void); >>> @@ -257,6 +259,11 @@ static inline bool >>> current_cpuset_is_being_rebound(void) >>>       return false; >>>   } >>> +static inline bool test_cpu_in_current_cpuset(int cpu) >>> +{ >>> +    return false; >>> +} >>> + >>>   static inline void rebuild_sched_domains(void) >>>   { >>>       partition_sched_domains(1, NULL, NULL); >>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c >>> index adb5190c4429..a63c27e9430e 100644 >>> --- a/kernel/cgroup/cpuset.c >>> +++ b/kernel/cgroup/cpuset.c >>> @@ -1849,6 +1849,17 @@ bool current_cpuset_is_being_rebound(void) >>>       return ret; >>>   } >>> +bool test_cpu_in_current_cpuset(int cpu) >>> +{ >>> +    bool ret; >>> + >>> +    rcu_read_lock(); >>> +    ret = cpumask_test_cpu(cpu, task_cs(current)->effective_cpus); >>> +    rcu_read_unlock(); >>> + >>> +    return ret; >>> +} >>> + >>>   static int update_relax_domain_level(struct cpuset *cs, s64 val) >>>   { >>>   #ifdef CONFIG_SMP >> >> In terms of review and so forth, I'd split this into a prep patch. Then >> patch 2 just becomes the io_uring consumer of it. >>