[lkml]   [2019]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] async: Let kfree() out of the critical area of the lock
On Thu, Sep 26, 2019 at 03:58:36PM +0800, Yunfeng Ye wrote:
> On 2019/9/25 23:20, Alexander Duyck wrote:
> > On Wed, 2019-09-25 at 20:52 +0800, Yunfeng Ye wrote:
> > It probably wouldn't hurt to update the patch description to mention that
> > async_schedule_node_domain does the allocation outside of the lock, then
> > takes the lock and does the list addition and entry_count increment inside
> > the critical section so this is just updating the code to match that it
> > seems.
> >
> > Otherwise the change itself looks safe to me, though I am not sure there
> > is a performance gain to be had so this is mostly just a cosmetic patch.
> >
> The async_lock is big global lock, I think it's good to put kfree() outside
> to keep the critical area as short as possible.

Agreed, kfree is not always cheap. We had patches in btrfs moving kfree
out of critical section(s) after causing softlockups due to increased lock

 \ /
  Last update: 2019-09-26 13:07    [W:0.071 / U:1.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site