Re: [PATCH] mm, sparse: drop pgdat_resize_lock in sparse_add/remove_one_section()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2018-11-27 09:00, Michal Hocko wrote:
[I am mostly offline and will be so tomorrow as well]

On Tue 27-11-18 08:52:14, osalvador@xxxxxxx wrote:
[...]
So, although removing the lock here is pretty straightforward, it does not really get us closer to that goal IMHO, if that is what we want to do in the
end.

But it doesn't get us further either, right? This patch shouldn't make
any plan for range locking any worse. Both adding and removing a sparse
section is pfn range defined unless I am missing something.

Yes, you are right, it should not have any impact.
It just felt like "we do already have the global lock, so let us stick with that".
But the less unneeded locks we have in our way, the better.

Sorry for the confusion.





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux