[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z-7apFKJK5u-7xL9@kbusch-mbp>
Date: Thu, 3 Apr 2025 12:59:48 -0600
From: Keith Busch <kbusch@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Kamaljit Singh <kamaljit.singh1@....com>, axboe@...nel.dk,
sagi@...mberg.me, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org, niklas.cassel@....com,
damien.lemoal@....com
Subject: Re: [PATCH v1 1/1] nvme: add admin controller support. prohibit ioq
creation for admin & disco ctrlrs
On Thu, Apr 03, 2025 at 06:49:01AM +0200, Christoph Hellwig wrote:
> On Mon, Mar 31, 2025 at 09:03:11AM -0600, Keith Busch wrote:
> > On Fri, Mar 28, 2025 at 02:36:40PM -0700, Kamaljit Singh wrote:
> > > -static inline bool nvme_discovery_ctrl(struct nvme_ctrl *ctrl)
> > > -{
> > > - return ctrl->opts && ctrl->opts->discovery_nqn;
> > > -}
> > > -
> >
> > I suppose it's fine to rename this function with an nvmf_ prefix, but
> > it's not really related to the rest of the patch and makes the diff
> > larger than necessary.
>
> It isn't, nvmf_ is really for code in the fabrics library and not used
> by core code.
Yes, I'm not suggesting to use "nvmf_" in the core. This function checks
for ctrl->ops, which only applies to fabrics, so this is a fabrics
specific function that could belong there instead of the core, is all
I'm saying. Not that I'd recommend making such a move in this patch...
Powered by blists - more mailing lists