lkml.org 
[lkml]   [2015]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] hugetlb: cond_resched for set_max_huge_pages and follow_hugetlb_page
On Thu, 23 Jul 2015, Jörn Engel wrote:

> > The loop is dropping the lock simply to do the allocation and it needs to
> > compare with the user-written number of hugepages to allocate.
>
> And at this point the existing code is racy. Page allocation might
> block for minutes trying to free some memory. A cond_resched doesn't
> change that - it only increases the odds of hitting the race window.
>

The existing code has always been racy, it explicitly admits this, the
problem is that your patch is making the race window larger.

> Are we looking at the same code? Mine looks like this:
> while (count > persistent_huge_pages(h)) {
> /*
> * If this allocation races such that we no longer need the
> * page, free_huge_page will handle it by freeing the page
> * and reducing the surplus.
> */
> spin_unlock(&hugetlb_lock);
> if (hstate_is_gigantic(h))
> ret = alloc_fresh_gigantic_page(h, nodes_allowed);
> else
> ret = alloc_fresh_huge_page(h, nodes_allowed);
> spin_lock(&hugetlb_lock);
> if (!ret)
> goto out;
>
> /* Bail for signals. Probably ctrl-c from user */
> if (signal_pending(current))
> goto out;
> }
>

I don't see the cond_resched() you propose to add, but the need for it is
obvious with a large user-written nr_hugepages in the above loop.

The suggestion is to check the conditional, reschedule if needed (and if
so, recheck the conditional), and then allocate.

Your third option looks fine and the best place to do the cond_resched().
I was looking at your second option when I responded and compared it to
the first. We don't want to do cond_resched() immediately before or after
the allocation, the net result is the same: we may be pointlessly
allocating the hugepage and each hugepage allocation can be very
heavyweight.

So I agree with your third option from the previous email.

You may also want to include the actual text of the warning from the
kernel log in your commit message. When people encounter this, then will
probably grep in the kernel logs for some keywords to see if it was
already fixed and I fear your current commit message may allow it to be
missed.
\
 
 \ /
  Last update: 2015-07-24 22:01    [W:0.068 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site