Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Michal Hocko <mhocko@xxxxxxxxxx>
- Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Date: Thu, 31 Mar 2016 11:20:05 +0200
- Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, Chris Zankel <chris@xxxxxxxxxx>, Max Filippov <jcmvbkbc@xxxxxxxxx>, x86@xxxxxxxxxx, linux-alpha@xxxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, sparclinux@xxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx
- In-reply-to: <20160331085926.GB27831@dhcp22.suse.cz>
- List-id: <linux-ia64.vger.kernel.org>
- References: <1456750705-7141-1-git-send-email-mhocko@kernel.org> <20160330133217.GV3408@twins.programming.kicks-ass.net> <20160331085926.GB27831@dhcp22.suse.cz>
- User-agent: Mutt/1.5.23 (2014-03-12)
* Michal Hocko <mhocko@xxxxxxxxxx> wrote:
> On Wed 30-03-16 15:32:17, Peter Zijlstra wrote:
> > On Mon, Feb 29, 2016 at 01:58:14PM +0100, Michal Hocko wrote:
> > > I have tested on x86 with OOM situations with high mmap_sem contention
> > > (basically many parallel page faults racing with many parallel mmap/munmap
> > > tight loops) so the waiters for the write locks are routinely interrupted
> > > by SIGKILL.
> >
> > Aside from the one niggle (as per the other email) they look good to me
> > and I would take them through the tip/locking tree.
>
> Thanks for the review! I understand that tip/locking would be the most
> appropriate place [...]
Yes.
> [...] but I am wondering whether this causes some issues with the follow up
> patches which use this new API and which I expect to go via Andrew's tree.
So AFAIK Andrew's tree is based on top of linux-next, so once it goes into
tip:locking/core, -mm can pick it up as well 1-2 days later.
Please send the changes in isolation, for merge into the locking tree.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]