From:   Jens Axboe <axboe@kernel.dk>
To:     io-uring@vger.kernel.org,
        =?utf-8?q?Michal_Koutn=C3=BD?= <mkoutny@suse.com>
Cc:     linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
        Pavel Begunkov <asml.silence@gmail.com>,
        Daniel Dao <dqminh@cloudflare.com>,
        Waiman Long <longman@redhat.com>
In-Reply-To: <20230314183332.25834-1-mkoutny@suse.com>
References: <20230314183332.25834-1-mkoutny@suse.com>
Subject: Re: [PATCH] io_uring/sqpoll: Do not set PF_NO_SETAFFINITY on
 sqpoll threads
Message-Id: <167888467141.25248.3419360093103116663.b4-ty@kernel.dk>
Date:   Wed, 15 Mar 2023 06:51:11 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Tue, 14 Mar 2023 19:33:32 +0100, Michal Koutný wrote:
> Users may specify a CPU where the sqpoll thread would run. This may
> conflict with cpuset operations because of strict PF_NO_SETAFFINITY
> requirement. That flag is unnecessary for polling "kernel" threads, see
> the reasoning in commit 01e68ce08a30 ("io_uring/io-wq: stop setting
> PF_NO_SETAFFINITY on io-wq workers"). Drop the flag on poll threads too.
> 
> 
> [...]

Applied, thanks!

[1/1] io_uring/sqpoll: Do not set PF_NO_SETAFFINITY on sqpoll threads
      commit: a5fc1441af7719e93dc7a638a960befb694ade89

Best regards,
-- 
Jens Axboe