From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH 14/15] libnvdimm: support read-only btt backing devices Date: Mon, 22 Jun 2015 15:11:05 -0400 Message-ID: References: <20150622063028.GA30434@lst.de> <20150622072844.GA31263@lst.de> <20150622154138.GC7952@lst.de> <20150622163224.GA9168@lst.de> <20150622164804.GA9393@lst.de> Mime-Version: 1.0 Content-Type: text/plain Cc: Christoph Hellwig , Jens Axboe , "linux-nvdimm\@lists.01.org" , "linux-kernel\@vger.kernel.org" , Linux ACPI , linux-fsdevel , Ingo Molnar To: Dan Williams Return-path: In-Reply-To: (Dan Williams's message of "Mon, 22 Jun 2015 12:04:05 -0700") Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Dan Williams writes: >>> Direct I/O using application can make assumption if they know the sector >>> size, and we must have a way for them to be able to see our new >>> "subsector sector size". >> >> You need to let them determine that when NOT using the btt, yes. Right >> now, I don't think there's a way to determine what the underlying atomic >> write unit is. That's something the NFIT spec probably should have >> defined. > > There are no atomic write units for NFIT to advertise beyond cpu register width. That would be useful information for the platform to provide, instead of requiring the o/s or applications to infer it. Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in