RE: [PATCH v3] ib_umem_release should decrement mm->pinned_vm from ib_umem_get

2014-09-15 Thread Shachar Raindel
; Yishai Hadas; Or > Gerlitz; Haggai Eran; Shachar Raindel; Christoph Lameter; Shawn Bohrer > Subject: [PATCH v3] ib_umem_release should decrement mm->pinned_vm from > ib_umem_get > > From: Shawn Bohrer > > In debugging an application that receives -ENOMEM from ib_reg_mr() I &

Re: [PATCH v3] ib_umem_release should decrement mm->pinned_vm from ib_umem_get

2014-09-15 Thread Shawn Bohrer
On Wed, Sep 03, 2014 at 12:13:57PM -0500, Shawn Bohrer wrote: > From: Shawn Bohrer > > In debugging an application that receives -ENOMEM from ib_reg_mr() I > found that ib_umem_get() can fail because the pinned_vm count has > wrapped causing it to always be larger than the lock limit even with >

[PATCH v3] ib_umem_release should decrement mm->pinned_vm from ib_umem_get

2014-09-03 Thread Shawn Bohrer
From: Shawn Bohrer In debugging an application that receives -ENOMEM from ib_reg_mr() I found that ib_umem_get() can fail because the pinned_vm count has wrapped causing it to always be larger than the lock limit even with RLIMIT_MEMLOCK set to RLIM_INFINITY. The wrapping of pinned_vm occurs bec