All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: <almasrymina@google.com>, <asml.silence@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	<cratiu@nvidia.com>, <parav@nvidia.com>, <netdev@vger.kernel.org>,
	<sdf@meta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v4 1/7] queue_api: add support for fetching per queue DMA dev
Date: Wed, 20 Aug 2025 18:01:00 -0700	[thread overview]
Message-ID: <20250820180100.7085a7d3@kernel.org> (raw)
In-Reply-To: <20250820171214.3597901-3-dtatulea@nvidia.com>

On Wed, 20 Aug 2025 20:11:52 +0300 Dragos Tatulea wrote:
> + * @ndo_queue_get_dma_dev: Get dma device for zero-copy operations to be used
> + *			   for this queue. When such device is not available,
> + *			   the function will return NULL.

nit: I think you're using a different tense/grammar than the doc for
other callbacks (which is admittedly somewhat unusual :$) 
Also should we indicate that "not available" is an error? Maybe just:

	Get dma device for zero-copy operations to be used
	for this queue. Return NULL on error.

>   * Note that @ndo_queue_mem_alloc and @ndo_queue_mem_free may be called while
>   * the interface is closed. @ndo_queue_start and @ndo_queue_stop will only
>   * be called for an interface which is open.

> +/**
> + * netdev_queue_get_dma_dev() - get dma device for zero-copy operations
> + * @dev:	net_device
> + * @idx:	queue index
> + *
> + * Get dma device for zero-copy operations to be used for this queue.
> + * When such device is not available or valid, the function will return NULL.

Unfortunately kdoc really wants us to add Return: statements to all
functions...

> + */
> +struct device *netdev_queue_get_dma_dev(struct net_device *dev, int idx)
> +{
> +	const struct netdev_queue_mgmt_ops *queue_ops = dev->queue_mgmt_ops;
> +	struct device *dma_dev;
> +
> +	if (queue_ops && queue_ops->ndo_queue_get_dma_dev)
> +		dma_dev = queue_ops->ndo_queue_get_dma_dev(dev, idx);
> +	else
> +		dma_dev = dev->dev.parent;
> +
> +	return dma_dev && dma_dev->dma_mask ? dma_dev : NULL;
> +}
> +EXPORT_SYMBOL(netdev_queue_get_dma_dev);
> \ No newline at end of file

This is in desperate need of a terminating new line.

But also -- why the export? iouring and devmem can't be modules.

  parent reply	other threads:[~2025-08-21  1:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 17:11 [PATCH net-next v4 0/7] devmem/io_uring: allow more flexibility for ZC DMA devices Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 1/7] queue_api: add support for fetching per queue DMA dev Dragos Tatulea
2025-08-20 22:48   ` Mina Almasry
2025-08-21  1:01   ` Jakub Kicinski [this message]
2025-08-21 11:06     ` Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 2/7] io_uring/zcrx: add support for custom DMA devices Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 3/7] net: devmem: get netdev DMA device via new API Dragos Tatulea
2025-08-21  1:04   ` Jakub Kicinski
2025-08-20 17:11 ` [PATCH net-next v4 4/7] net/mlx5e: add op for getting netdev DMA device Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 5/7] net: devmem: pull out dma_dev out of net_devmem_bind_dmabuf Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 6/7] net: devmem: pre-read requested rx queues during bind Dragos Tatulea
2025-08-20 22:51   ` Mina Almasry
2025-08-21  1:09   ` Jakub Kicinski
2025-08-21 11:07     ` Dragos Tatulea
2025-08-20 17:11 ` [PATCH net-next v4 7/7] net: devmem: allow binding on rx queues with same DMA devices Dragos Tatulea
2025-08-20 22:57   ` Mina Almasry
2025-08-21 16:37     ` Dragos Tatulea
2025-08-21  1:16   ` Jakub Kicinski
2025-08-21 11:10     ` Dragos Tatulea
2025-08-21 14:32       ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250820180100.7085a7d3@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=sdf@meta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.