From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Date: Fri, 01 Apr 2016 06:33:48 +0000 Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore Message-Id: <20160401063348.GA6815@gmail.com> List-Id: References: <1456750705-7141-1-git-send-email-mhocko@kernel.org> <20160330133217.GV3408@twins.programming.kicks-ass.net> <20160331085926.GB27831@dhcp22.suse.cz> <20160331092005.GA18640@gmail.com> <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> In-Reply-To: <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrew Morton Cc: Michal Hocko , Peter Zijlstra , LKML , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , "David S. Miller" , Tony Luck , Chris Zankel , Max Filippov , x86@kernel.org, linux-alpha@vger.kernel.org, linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org * Andrew Morton wrote: > On Thu, 31 Mar 2016 11:20:05 +0200 Ingo Molnar wrote: > > > So AFAIK Andrew's tree is based on top of linux-next > > Not really true any more - I only base -mm patches on linux-next > patches when they must be based that way due to some known dependency. > > I can certainly handle MM patches which are based on linux-next. Such > an arrangement is going to make life awkward for Michal's > auto-maintained git tree of the -mm MM patches > (git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git). > > Maybe I could merge down_write_killable into -mm's main MM section then > knock it out of my copy of linux-next, so everything is seamless for > mm.git. I've done that before. > > But it's all a bit of a pain - it would be simpler to keep > down_write_killable in the same tree as the patches which depend on it. I can help on the Git level: I can do tip:locking/rwsem tree with only these changes, with stable sha1's, on which the remaining work can be based. The locking tree typically goes in early during the merge window, so there's no real dependencies. On the source code level this series is changing the existing locking code too, it doesn't just add a new orthogonal method or so, so I'd really like to have it in the locking tree. Thanks, Ingo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758219AbcDAGd5 (ORCPT ); Fri, 1 Apr 2016 02:33:57 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34203 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753428AbcDAGdy (ORCPT ); Fri, 1 Apr 2016 02:33:54 -0400 Date: Fri, 1 Apr 2016 08:33:48 +0200 From: Ingo Molnar To: Andrew Morton Cc: Michal Hocko , Peter Zijlstra , LKML , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , "David S. Miller" , Tony Luck , Chris Zankel , Max Filippov , x86@kernel.org, linux-alpha@vger.kernel.org, linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore Message-ID: <20160401063348.GA6815@gmail.com> References: <1456750705-7141-1-git-send-email-mhocko@kernel.org> <20160330133217.GV3408@twins.programming.kicks-ass.net> <20160331085926.GB27831@dhcp22.suse.cz> <20160331092005.GA18640@gmail.com> <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andrew Morton wrote: > On Thu, 31 Mar 2016 11:20:05 +0200 Ingo Molnar wrote: > > > So AFAIK Andrew's tree is based on top of linux-next > > Not really true any more - I only base -mm patches on linux-next > patches when they must be based that way due to some known dependency. > > I can certainly handle MM patches which are based on linux-next. Such > an arrangement is going to make life awkward for Michal's > auto-maintained git tree of the -mm MM patches > (git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git). > > Maybe I could merge down_write_killable into -mm's main MM section then > knock it out of my copy of linux-next, so everything is seamless for > mm.git. I've done that before. > > But it's all a bit of a pain - it would be simpler to keep > down_write_killable in the same tree as the patches which depend on it. I can help on the Git level: I can do tip:locking/rwsem tree with only these changes, with stable sha1's, on which the remaining work can be based. The locking tree typically goes in early during the merge window, so there's no real dependencies. On the source code level this series is changing the existing locking code too, it doesn't just add a new orthogonal method or so, so I'd really like to have it in the locking tree. Thanks, Ingo