public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
* [PATCH v2] nvme: change the return type of nvme_poll()
@ 2024-12-09 13:33 Yongsoo Joo
  2024-12-09 15:44 ` Keith Busch
  0 siblings, 1 reply; 5+ messages in thread
From: Yongsoo Joo @ 2024-12-09 13:33 UTC (permalink / raw)
  To: kbusch, axboe, hch, sagi; +Cc: linux-nvme, Yongsoo Joo

Change the return type of nvme_poll() to bool to reflect its boolean
return value.

Signed-off-by: Yongsoo Joo <ysjoo@kookmin.ac.kr>
---
Changes from v1 to v2:
- Changed the return type of nvme_poll() from int to bool, rather than
  modifying the internal return variable from bool to int (Christoph
  Hellwig).
- Updated the patch subject by replacing "fix" with "change" (Keith 
  Busch).

 drivers/nvme/host/pci.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 1a5ba80f1811..34650c03c120 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -1206,7 +1206,7 @@ static void nvme_poll_irqdisable(struct nvme_queue *nvmeq)
 	enable_irq(pci_irq_vector(pdev, nvmeq->cq_vector));
 }
 
-static int nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
+static bool nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
 {
 	struct nvme_queue *nvmeq = hctx->driver_data;
 	bool found;
-- 
2.34.1


-- 



^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] nvme: change the return type of nvme_poll()
  2024-12-09 13:33 [PATCH v2] nvme: change the return type of nvme_poll() Yongsoo Joo
@ 2024-12-09 15:44 ` Keith Busch
  2024-12-09 21:39   ` Yongsoo Joo
  0 siblings, 1 reply; 5+ messages in thread
From: Keith Busch @ 2024-12-09 15:44 UTC (permalink / raw)
  To: Yongsoo Joo; +Cc: axboe, hch, sagi, linux-nvme

On Mon, Dec 09, 2024 at 01:33:44PM +0000, Yongsoo Joo wrote:
> -static int nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> +static bool nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
>  {
>  	struct nvme_queue *nvmeq = hctx->driver_data;
>  	bool found;
> -- 

This function is registered with blk_mq_ops, so you would have to change
the prototype there too, and every other driver that also registers a
poll op. Honestly, it may not be worth the effort.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] nvme: change the return type of nvme_poll()
  2024-12-09 15:44 ` Keith Busch
@ 2024-12-09 21:39   ` Yongsoo Joo
  2024-12-10  0:01     ` Keith Busch
  0 siblings, 1 reply; 5+ messages in thread
From: Yongsoo Joo @ 2024-12-09 21:39 UTC (permalink / raw)
  To: Keith Busch; +Cc: axboe, hch, sagi, linux-nvme

On Mon, Dec 09, 2024 at 08:44:28AM -0700, Keith Busch wrote:
> On Mon, Dec 09, 2024 at 01:33:44PM +0000, Yongsoo Joo wrote:
> > -static int nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> > +static bool nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> >  {
> >  	struct nvme_queue *nvmeq = hctx->driver_data;
> >  	bool found;
> > -- 
> 
> This function is registered with blk_mq_ops, so you would have to change
> the prototype there too, and every other driver that also registers a
> poll op. Honestly, it may not be worth the effort.
Oh, I overlooked the issue you pointed out, which brings me back to my initial 
suggestion. The function nvme_poll_cq() returns the number of found CQEs, but 
nvme_poll() seems to unnecessarily reduce this information to a boolean.
A minimal change from “bool found” to “int found” in nvme_poll() would 
preserve this information, allowing any interested researcher to make use of 
it. Also, the description of poll in blk_mq_ops can be expanded as follows:
	/**
	 * @poll: Called to poll for completion of a specific tag.
         * Returns the number of CQEs found.
	 */
Thank you for your time, and I look forward to hearing your opinion.

-- 



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] nvme: change the return type of nvme_poll()
  2024-12-09 21:39   ` Yongsoo Joo
@ 2024-12-10  0:01     ` Keith Busch
  2024-12-10  0:37       ` Yongsoo Joo
  0 siblings, 1 reply; 5+ messages in thread
From: Keith Busch @ 2024-12-10  0:01 UTC (permalink / raw)
  To: Yongsoo Joo; +Cc: axboe, hch, sagi, linux-nvme

On Mon, Dec 09, 2024 at 09:39:42PM +0000, Yongsoo Joo wrote:
> On Mon, Dec 09, 2024 at 08:44:28AM -0700, Keith Busch wrote:
> > On Mon, Dec 09, 2024 at 01:33:44PM +0000, Yongsoo Joo wrote:
> > > -static int nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> > > +static bool nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> > >  {
> > >  	struct nvme_queue *nvmeq = hctx->driver_data;
> > >  	bool found;
> > > -- 
> > 
> > This function is registered with blk_mq_ops, so you would have to change
> > the prototype there too, and every other driver that also registers a
> > poll op. Honestly, it may not be worth the effort.
> Oh, I overlooked the issue you pointed out, which brings me back to my initial 
> suggestion. The function nvme_poll_cq() returns the number of found CQEs, but 
> nvme_poll() seems to unnecessarily reduce this information to a boolean.

Can we just change nvme_poll_cq() instead to return a bool instead?

---
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 4c644bb7f0692..54910f8eadff8 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -1148,13 +1148,13 @@ static inline void nvme_update_cq_head(struct nvme_queue *nvmeq)
 	}
 }
 
-static inline int nvme_poll_cq(struct nvme_queue *nvmeq,
-			       struct io_comp_batch *iob)
+static inline bool nvme_poll_cq(struct nvme_queue *nvmeq,
+				struct io_comp_batch *iob)
 {
-	int found = 0;
+	bool found = false;
 
 	while (nvme_cqe_pending(nvmeq)) {
-		found++;
+		found = true
 		/*
 		 * load-load control dependency between phase and the rest of
 		 * the cqe requires a full read memory barrier
--

> A minimal change from "bool found" to "int found" in nvme_poll() would 
> preserve this information, allowing any interested researcher to make use of 
> it. Also, the description of poll in blk_mq_ops can be expanded as follows:
>        /**
>         * @poll: Called to poll for completion of a specific tag.
>         * Returns the number of CQEs found.
>         */

Since you pointed this comment out, I see it is from an earlier versions
of this interface and outdated. The current behavior polls for any
completion rather than a specific tag.


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] nvme: change the return type of nvme_poll()
  2024-12-10  0:01     ` Keith Busch
@ 2024-12-10  0:37       ` Yongsoo Joo
  0 siblings, 0 replies; 5+ messages in thread
From: Yongsoo Joo @ 2024-12-10  0:37 UTC (permalink / raw)
  To: Keith Busch; +Cc: axboe, hch, sagi, linux-nvme

On Mon, Dec 09, 2024 at 05:01:06PM -0700, Keith Busch wrote:
> On Mon, Dec 09, 2024 at 09:39:42PM +0000, Yongsoo Joo wrote:
> > On Mon, Dec 09, 2024 at 08:44:28AM -0700, Keith Busch wrote:
> > > On Mon, Dec 09, 2024 at 01:33:44PM +0000, Yongsoo Joo wrote:
> > > > -static int nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> > > > +static bool nvme_poll(struct blk_mq_hw_ctx *hctx, struct io_comp_batch *iob)
> > > >  {
> > > >  	struct nvme_queue *nvmeq = hctx->driver_data;
> > > >  	bool found;
> > > > -- 
> > > 
> > > This function is registered with blk_mq_ops, so you would have to change
> > > the prototype there too, and every other driver that also registers a
> > > poll op. Honestly, it may not be worth the effort.
> > Oh, I overlooked the issue you pointed out, which brings me back to my initial 
> > suggestion. The function nvme_poll_cq() returns the number of found CQEs, but 
> > nvme_poll() seems to unnecessarily reduce this information to a boolean.
> 
> Can we just change nvme_poll_cq() instead to return a bool instead?

Thank you for your suggestion; it makes sense to me. We could consider modifying 
nvme_poll() to return the number of CQEs in the future when specific use cases 
arise. 
> 
> ---
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 4c644bb7f0692..54910f8eadff8 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -1148,13 +1148,13 @@ static inline void nvme_update_cq_head(struct nvme_queue *nvmeq)
>  	}
>  }
>  
> -static inline int nvme_poll_cq(struct nvme_queue *nvmeq,
> -			       struct io_comp_batch *iob)
> +static inline bool nvme_poll_cq(struct nvme_queue *nvmeq,
> +				struct io_comp_batch *iob)
>  {
> -	int found = 0;
> +	bool found = false;
>  
>  	while (nvme_cqe_pending(nvmeq)) {
> -		found++;
> +		found = true

  +             found = true;

>  		/*
>  		 * load-load control dependency between phase and the rest of
>  		 * the cqe requires a full read memory barrier
> --
> 
> > A minimal change from "bool found" to "int found" in nvme_poll() would 
> > preserve this information, allowing any interested researcher to make use of 
> > it. Also, the description of poll in blk_mq_ops can be expanded as follows:
> >        /**
> >         * @poll: Called to poll for completion of a specific tag.
            * @poll: Called to poll for completion of any CQE.
> >         * Returns the number of CQEs found.
> >         */
> 
> Since you pointed this comment out, I see it is from an earlier versions
> of this interface and outdated. The current behavior polls for any
> completion rather than a specific tag.
Oh, I see. How about revising the comment to "Called to poll for the 
completion of any CQE"? Do you think this change should be submitted as a 
seperated patch?


-- 



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-12-10  0:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-12-09 13:33 [PATCH v2] nvme: change the return type of nvme_poll() Yongsoo Joo
2024-12-09 15:44 ` Keith Busch
2024-12-09 21:39   ` Yongsoo Joo
2024-12-10  0:01     ` Keith Busch
2024-12-10  0:37       ` Yongsoo Joo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox