Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932348AbbFQQrm (ORCPT ); Wed, 17 Jun 2015 12:47:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48968 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757644AbbFQQr0 (ORCPT ); Wed, 17 Jun 2015 12:47:26 -0400 From: Jeff Moyer To: Christoph Hellwig , Dan Williams Cc: Matthew Wilcox , axboe@kernel.dk, sfr@canb.auug.org.au, akpm@linux-foundation.org, rafael@kernel.org, neilb@suse.de, gregkh@linuxfoundation.org, linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org, mingo@kernel.org, linux-acpi@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH v5 17/21] libnvdimm: infrastructure for btt devices References: <20150602001134.4506.45867.stgit@dwillia2-desk3.amr.corp.intel.com> <20150602001541.4506.90125.stgit@dwillia2-desk3.amr.corp.intel.com> <20150609064200.GE9804@lst.de> <20150610184616.GL2729@linux.intel.com> <20150611072812.GB1905@lst.de> X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Wed, 17 Jun 2015 12:47:23 -0400 In-Reply-To: <20150611072812.GB1905@lst.de> (Christoph Hellwig's message of "Thu, 11 Jun 2015 09:28:12 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1219 Lines: 27 Christoph Hellwig writes: > On Wed, Jun 10, 2015 at 02:46:16PM -0400, Matthew Wilcox wrote: >> Don't screw up rw_page. The point of rw_page is to read or write a page >> cache page. It can sleep, and it indicates success by using the page >> flags. Don't try and scqueeze rw_bytes into it. If you want rw_bytes >> to be a queue operation, that's one thing, but don't mess with rw_page. > > Oh, I forgot about the page manipulating nature. Yes, we'll need a different > operation in this case. I didn't see this addressed in the new patch set. I'm also concerned about the layering, but I haven't put enough time into it to really make a better suggestion. I really dislike the idea of yet another device stacking model in the kernel and I'm worried the code will go in, and the sysfs interface will end up as a "user abi" and we won't be able to change it in the future. Dan, have you made any progress on this, or do you have plans to? Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/