From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: [PATCH 19/20] xfs: implement pNFS export operations Date: Sun, 8 Feb 2015 09:09:42 -0500 Message-ID: <20150208090942.51e99687@tlielax.poochiereds.net> References: <1421925006-24231-1-git-send-email-hch@lst.de> <1421925006-24231-20-git-send-email-hch@lst.de> <20150205004758.GO4251@dastard> <20150205070858.GA593@lst.de> <20150205135756.GA6386@lst.de> <20150206222047.GM12722@dastard> <20150206224258.GJ29783@fieldses.org> <20150208133435.GA27081@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "J. Bruce Fields" , Dave Chinner , Jeff Layton , linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org To: Christoph Hellwig Return-path: In-Reply-To: <20150208133435.GA27081-jcswGhMUV9g@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Sun, 8 Feb 2015 14:34:35 +0100 Christoph Hellwig wrote: > On Fri, Feb 06, 2015 at 05:42:58PM -0500, J. Bruce Fields wrote: > > You'd basically just be pulling my tree (Christoph's is just my nfsd > > tree with his patches on top, and I've been testing with exactly that > > locally, just putting off pushing it out till we decide this.) > > > > So anyway, fine with me if you want to just pull that into the xfs tree. > > Mine's ready whenever, so if I send my pull pretty soon after the merge > > window and you send it a little later then we still keep the property > > that Linus's merge still has a diffstat only in our respective areas. > > > > (OK, it's a little more complicated because I've got the same > > arrangement with jlayton, so the order is jlayton's lock pull, then my > > nfsd pull, then your xfs pull. Is this getting too complicated? > > jlayton and I are both ready to so and I think it'd work.) > > > > I'm also fine with duplicating those few patches, or whatever. > > Maybe the better idea is to pull the xfs tree in the nfsd tree, but > that would require Dave sending an early pull request so that the > nfsd pull doesn't get delayed. > > Or we just defer the pnfsd merge. While I tried to get it in in time > for 3.20 all the delays during review mean we're really late no and should > punt it to 3.21. FWIW, I plan to send a pull request for the locking changes as soon as the merge window opens. Hopefully that won't be an issue for long... -- Jeff Layton -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 5BCA77F54 for ; Sun, 8 Feb 2015 08:09:52 -0600 (CST) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by relay3.corp.sgi.com (Postfix) with ESMTP id D135BAC001 for ; Sun, 8 Feb 2015 06:09:48 -0800 (PST) Received: from mail-qg0-f42.google.com (mail-qg0-f42.google.com [209.85.192.42]) by cuda.sgi.com with ESMTP id VixnZc7H9T16HCDf (version=TLSv1 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 08 Feb 2015 06:09:46 -0800 (PST) Received: by mail-qg0-f42.google.com with SMTP id z107so12073717qgd.1 for ; Sun, 08 Feb 2015 06:09:45 -0800 (PST) Date: Sun, 8 Feb 2015 09:09:42 -0500 From: Jeff Layton Subject: Re: [PATCH 19/20] xfs: implement pNFS export operations Message-ID: <20150208090942.51e99687@tlielax.poochiereds.net> In-Reply-To: <20150208133435.GA27081@lst.de> References: <1421925006-24231-1-git-send-email-hch@lst.de> <1421925006-24231-20-git-send-email-hch@lst.de> <20150205004758.GO4251@dastard> <20150205070858.GA593@lst.de> <20150205135756.GA6386@lst.de> <20150206222047.GM12722@dastard> <20150206224258.GJ29783@fieldses.org> <20150208133435.GA27081@lst.de> MIME-Version: 1.0 List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Christoph Hellwig Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com, "J. Bruce Fields" , Jeff Layton , linux-fsdevel@vger.kernel.org On Sun, 8 Feb 2015 14:34:35 +0100 Christoph Hellwig wrote: > On Fri, Feb 06, 2015 at 05:42:58PM -0500, J. Bruce Fields wrote: > > You'd basically just be pulling my tree (Christoph's is just my nfsd > > tree with his patches on top, and I've been testing with exactly that > > locally, just putting off pushing it out till we decide this.) > > > > So anyway, fine with me if you want to just pull that into the xfs tree. > > Mine's ready whenever, so if I send my pull pretty soon after the merge > > window and you send it a little later then we still keep the property > > that Linus's merge still has a diffstat only in our respective areas. > > > > (OK, it's a little more complicated because I've got the same > > arrangement with jlayton, so the order is jlayton's lock pull, then my > > nfsd pull, then your xfs pull. Is this getting too complicated? > > jlayton and I are both ready to so and I think it'd work.) > > > > I'm also fine with duplicating those few patches, or whatever. > > Maybe the better idea is to pull the xfs tree in the nfsd tree, but > that would require Dave sending an early pull request so that the > nfsd pull doesn't get delayed. > > Or we just defer the pnfsd merge. While I tried to get it in in time > for 3.20 all the delays during review mean we're really late no and should > punt it to 3.21. FWIW, I plan to send a pull request for the locking changes as soon as the merge window opens. Hopefully that won't be an issue for long... -- Jeff Layton _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail-qc0-f181.google.com ([209.85.216.181]:42351 "EHLO mail-qc0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751216AbbBHOJq (ORCPT ); Sun, 8 Feb 2015 09:09:46 -0500 Received: by mail-qc0-f181.google.com with SMTP id p6so3157506qcv.12 for ; Sun, 08 Feb 2015 06:09:45 -0800 (PST) Date: Sun, 8 Feb 2015 09:09:42 -0500 From: Jeff Layton To: Christoph Hellwig Cc: "J. Bruce Fields" , Dave Chinner , Jeff Layton , linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: [PATCH 19/20] xfs: implement pNFS export operations Message-ID: <20150208090942.51e99687@tlielax.poochiereds.net> In-Reply-To: <20150208133435.GA27081@lst.de> References: <1421925006-24231-1-git-send-email-hch@lst.de> <1421925006-24231-20-git-send-email-hch@lst.de> <20150205004758.GO4251@dastard> <20150205070858.GA593@lst.de> <20150205135756.GA6386@lst.de> <20150206222047.GM12722@dastard> <20150206224258.GJ29783@fieldses.org> <20150208133435.GA27081@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-nfs-owner@vger.kernel.org List-ID: On Sun, 8 Feb 2015 14:34:35 +0100 Christoph Hellwig wrote: > On Fri, Feb 06, 2015 at 05:42:58PM -0500, J. Bruce Fields wrote: > > You'd basically just be pulling my tree (Christoph's is just my nfsd > > tree with his patches on top, and I've been testing with exactly that > > locally, just putting off pushing it out till we decide this.) > > > > So anyway, fine with me if you want to just pull that into the xfs tree. > > Mine's ready whenever, so if I send my pull pretty soon after the merge > > window and you send it a little later then we still keep the property > > that Linus's merge still has a diffstat only in our respective areas. > > > > (OK, it's a little more complicated because I've got the same > > arrangement with jlayton, so the order is jlayton's lock pull, then my > > nfsd pull, then your xfs pull. Is this getting too complicated? > > jlayton and I are both ready to so and I think it'd work.) > > > > I'm also fine with duplicating those few patches, or whatever. > > Maybe the better idea is to pull the xfs tree in the nfsd tree, but > that would require Dave sending an early pull request so that the > nfsd pull doesn't get delayed. > > Or we just defer the pnfsd merge. While I tried to get it in in time > for 3.20 all the delays during review mean we're really late no and should > punt it to 3.21. FWIW, I plan to send a pull request for the locking changes as soon as the merge window opens. Hopefully that won't be an issue for long... -- Jeff Layton