On Thu, Feb 20, 2020 at 08:57:33AM +, Julien Grall wrote:
>
>
> On 20/02/2020 08:36, Jan Beulich wrote:
> > On 20.02.2020 09:27, Jürgen Groß wrote:
> > > On 20.02.20 09:13, Jan Beulich wrote:
> > > > On 13.02.2020 12:32, Roger Pau Monne wrote:
> > > > > Most users of the cpu maps just care ab
On 20/02/2020 08:36, Jan Beulich wrote:
On 20.02.2020 09:27, Jürgen Groß wrote:
On 20.02.20 09:13, Jan Beulich wrote:
On 13.02.2020 12:32, Roger Pau Monne wrote:
Most users of the cpu maps just care about the maps not changing while
the lock is being held, but don't actually modify the maps.
On 20.02.2020 09:27, Jürgen Groß wrote:
> On 20.02.20 09:13, Jan Beulich wrote:
>> On 13.02.2020 12:32, Roger Pau Monne wrote:
>>> Most users of the cpu maps just care about the maps not changing while
>>> the lock is being held, but don't actually modify the maps.
>>>
>>> Convert the lock into a r
On 20.02.20 09:13, Jan Beulich wrote:
On 13.02.2020 12:32, Roger Pau Monne wrote:
Most users of the cpu maps just care about the maps not changing while
the lock is being held, but don't actually modify the maps.
Convert the lock into a rw lock, and take the lock in read mode in
get_cpu_maps an
On 13.02.2020 12:32, Roger Pau Monne wrote:
> Most users of the cpu maps just care about the maps not changing while
> the lock is being held, but don't actually modify the maps.
>
> Convert the lock into a rw lock, and take the lock in read mode in
> get_cpu_maps and in write mode in cpu_hotplug_
On Wed, Feb 19, 2020 at 02:42:58PM +0100, Jan Beulich wrote:
> On 19.02.2020 14:19, Roger Pau Monné wrote:
> > On Wed, Feb 19, 2020 at 01:56:02PM +0100, Jan Beulich wrote:
> >> On 13.02.2020 12:32, Roger Pau Monne wrote:
> >>> void __init register_cpu_notifier(struct notifier_block *nb)
> >>> {
>
On 19.02.2020 14:19, Roger Pau Monné wrote:
> On Wed, Feb 19, 2020 at 01:56:02PM +0100, Jan Beulich wrote:
>> On 13.02.2020 12:32, Roger Pau Monne wrote:
>>> void __init register_cpu_notifier(struct notifier_block *nb)
>>> {
>>> -if ( !spin_trylock(&cpu_add_remove_lock) )
>>> +if ( !write
On Wed, Feb 19, 2020 at 01:56:02PM +0100, Jan Beulich wrote:
> On 13.02.2020 12:32, Roger Pau Monne wrote:
> > void __init register_cpu_notifier(struct notifier_block *nb)
> > {
> > -if ( !spin_trylock(&cpu_add_remove_lock) )
> > +if ( !write_trylock(&cpu_add_remove_lock) )
> > B
On 13.02.2020 12:32, Roger Pau Monne wrote:
> void __init register_cpu_notifier(struct notifier_block *nb)
> {
> -if ( !spin_trylock(&cpu_add_remove_lock) )
> +if ( !write_trylock(&cpu_add_remove_lock) )
> BUG(); /* Should never fail as we are called only during boot. */
> n
Hi Roger,
On 13/02/2020 11:32, Roger Pau Monne wrote:
Most users of the cpu maps just care about the maps not changing while
the lock is being held, but don't actually modify the maps.
Convert the lock into a rw lock, and take the lock in read mode in
get_cpu_maps and in write mode in cpu_hotpl
Most users of the cpu maps just care about the maps not changing while
the lock is being held, but don't actually modify the maps.
Convert the lock into a rw lock, and take the lock in read mode in
get_cpu_maps and in write mode in cpu_hotplug_begin. This will lower
the contention around the lock,
11 matches
Mail list logo
