Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753058AbbDPRSB (ORCPT ); Thu, 16 Apr 2015 13:18:01 -0400 Received: from mail-lb0-f173.google.com ([209.85.217.173]:33135 "EHLO mail-lb0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754315AbbDPRRw (ORCPT ); Thu, 16 Apr 2015 13:17:52 -0400 Message-ID: <552FEEBB.2010106@bjorling.me> Date: Thu, 16 Apr 2015 19:17:47 +0200 From: Matias Bjorling User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Keith Busch CC: hch@infradead.org, axboe@fb.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, javier@paletta.io Subject: Re: [PATCH 5/5 v2] nvme: LightNVM support References: <1429101284-19490-1-git-send-email-m@bjorling.me> <1429101284-19490-6-git-send-email-m@bjorling.me> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1940 Lines: 51 Den 16-04-2015 kl. 16:55 skrev Keith Busch: > On Wed, 15 Apr 2015, Matias Bjørling wrote: >> @@ -2316,7 +2686,9 @@ static int nvme_dev_add(struct nvme_dev *dev) >> struct nvme_id_ctrl *ctrl; >> void *mem; >> dma_addr_t dma_addr; >> - int shift = NVME_CAP_MPSMIN(readq(&dev->bar->cap)) + 12; >> + u64 cap = readq(&dev->bar->cap); >> + int shift = NVME_CAP_MPSMIN(cap) + 12; >> + int nvm_cmdset = NVME_CAP_NVM(cap); > > The controller capabilities' command sets supported used here is the > right way to key off on support for this new command set, IMHO, but I do > not see in this patch the command set being selected when the controller > is enabled I'll get that added. Wouldn't it just be that the command set always is selected? A NVMe controller can expose both normal and lightnvm namespaces. So we would always enable it, if CAP bit is set. > > Also if we're going this route, I think we need to define this reserved > bit in the spec, but I'm not sure how to help with that. Agree, we'll see how it can be proposed. > >> @@ -2332,6 +2704,7 @@ static int nvme_dev_add(struct nvme_dev *dev) >> ctrl = mem; >> nn = le32_to_cpup(&ctrl->nn); >> dev->oncs = le16_to_cpup(&ctrl->oncs); >> + dev->oacs = le16_to_cpup(&ctrl->oacs); > > I don't find OACS used anywhere in the rest of the patch. I think this > must be left over from v1. Oops, yes, that's just a left over. > > Otherwise it looks pretty good to me, but I think it would be cleaner if > the lightnvm stuff is not mixed in the same file with the standard nvme > command set. We might end up splitting nvme-core in the future anyway > for command sets and transports. Will do. Thanks. -- 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/