On Thu 23-07-15 14:54:31, Spencer Baugh wrote: > From: Joern Engel <jo...@logfs.org> > > ~150ms scheduler latency for both observed in the wild.
This is way to vague. Could you describe your problem somehow more, please? There are schduling points in the page allocator (when it triggers the reclaim), why are those not sufficient? Or do you manage to allocate many hugetlb pages without performing the reclaim and that leads to soft lockups? > > Signed-off-by: Joern Engel <jo...@logfs.org> > Signed-off-by: Spencer Baugh <sba...@catern.com> > --- > mm/hugetlb.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/mm/hugetlb.c b/mm/hugetlb.c > index a8c3087..2eb6919 100644 > --- a/mm/hugetlb.c > +++ b/mm/hugetlb.c > @@ -1836,6 +1836,7 @@ static unsigned long set_max_huge_pages(struct hstate > *h, unsigned long count, > ret = alloc_fresh_gigantic_page(h, nodes_allowed); > else > ret = alloc_fresh_huge_page(h, nodes_allowed); > + cond_resched(); > spin_lock(&hugetlb_lock); > if (!ret) > goto out; > @@ -3521,6 +3522,7 @@ long follow_hugetlb_page(struct mm_struct *mm, struct > vm_area_struct *vma, > spin_unlock(ptl); > ret = hugetlb_fault(mm, vma, vaddr, > (flags & FOLL_WRITE) ? FAULT_FLAG_WRITE : 0); > + cond_resched(); > if (!(ret & VM_FAULT_ERROR)) > continue; > > -- > 2.5.0.rc3 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
