[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d88d3e92-e9af-5ffd-9b9e-731255226f99@zytor.com>
Date: Sun, 25 Mar 2018 15:11:54 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Eric Dumazet <eric.dumazet@...il.com>,
Eric Dumazet <edumazet@...gle.com>, x86 <x86@...nel.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
Hugh Dickins <hughd@...gle.com>
Subject: Re: [PATCH v3 2/2] x86, cpuid: allow cpuid_read() to schedule
On 03/23/18 18:01, Eric Dumazet wrote:
>
> Indeed, assuming a daemon can have threads running on all cpus :/
>
> Some environments like to partition cpus for different jobs/containers.
>
Then it doesn't need to run it on all cpus... just the one that that
particular daemon is "responsible" for.
-hpa
Powered by blists - more mailing lists