Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-10 Thread Ingo Molnar
* Michal Hocko wrote: > > > Why? Each syscall already is killable as the task might be killed by the > > > OOM > > > killer. > > > > Not all syscalls are interruptible - for example sys_sync() isn't: > > I guess we are talking past each other. [...] Heh, you are being polite, I think what h

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Michal Hocko
On Wed 09-03-16 14:43:39, Ingo Molnar wrote: > > * Michal Hocko wrote: > > > On Wed 09-03-16 14:17:10, Ingo Molnar wrote: > > > > > > * Michal Hocko wrote: > > > > > > > > [...] this is a follow up work for oom_reaper [1]. As the async OOM > > > > > killing > > > > > depends on oom_sem fo

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Ingo Molnar
* Michal Hocko wrote: > On Wed 09-03-16 14:17:10, Ingo Molnar wrote: > > > > * Michal Hocko wrote: > > > > > > [...] this is a follow up work for oom_reaper [1]. As the async OOM > > > > killing > > > > depends on oom_sem for read we would really appreciate if a holder for > > > > write

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Michal Hocko
On Wed 09-03-16 14:17:10, Ingo Molnar wrote: > > * Michal Hocko wrote: > > > > [...] this is a follow up work for oom_reaper [1]. As the async OOM > > > killing > > > depends on oom_sem for read we would really appreciate if a holder for > > > write > > > stood in the way. This patchset i

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Ingo Molnar
* Michal Hocko wrote: > > [...] this is a follow up work for oom_reaper [1]. As the async OOM > > killing > > depends on oom_sem for read we would really appreciate if a holder for > > write > > stood in the way. This patchset is changing many of down_write calls to be > > killable to h

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Michal Hocko
On Wed 09-03-16 13:18:50, Ingo Molnar wrote: > > * Michal Hocko wrote: > > > Hi, > > > > the following patchset implements a killable variant of write lock for > > rw_semaphore. My usecase is to turn as many mmap_sem write users to use a > > killable variant which will be helpful for the oom_r

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-03-09 Thread Ingo Molnar
* Michal Hocko wrote: > Hi, > > the following patchset implements a killable variant of write lock for > rw_semaphore. My usecase is to turn as many mmap_sem write users to use a > killable variant which will be helpful for the oom_reaper [1] to > asynchronously > tear down the oom victim ad

Re: [RFC 0/12] introduce down_write_killable for rw_semaphore

2016-02-19 Thread Michal Hocko
Are there any fundamenta lobjections to the patchset? I plan to resubmit next week with the changes from the feedback along with the mmap_sem down_write_killable usage. On Tue 02-02-16 21:19:17, Michal Hocko wrote: > Hi, > the following patchset implements a killable variant of write lock for > rw

[RFC 0/12] introduce down_write_killable for rw_semaphore

2016-02-02 Thread Michal Hocko
Hi, the following patchset implements a killable variant of write lock for rw_semaphore. My usecase is to turn as many mmap_sem write users to use a killable variant which will be helpful for the oom_reaper [1] to asynchronously tear down the oom victim address space which requires mmap_sem for rea