netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: netdev@vger.kernel.org, "Björn Töpel" <bjorn@kernel.org>,
	"Magnus Karlsson" <magnus.karlsson@intel.com>,
	"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
	"Jonathan Lemon" <jonathan.lemon@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	bpf@vger.kernel.org, virtualization@lists.linux-foundation.org,
	"Jason Wang" <jasowang@redhat.com>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Christoph Hellwig" <hch@infradead.org>
Subject: Re: [PATCH net-next] xsk: introduce xsk_dma_ops
Date: Mon, 17 Apr 2023 02:43:32 -0400	[thread overview]
Message-ID: <20230417024216-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230417032750.7086-1-xuanzhuo@linux.alibaba.com>

On Mon, Apr 17, 2023 at 11:27:50AM +0800, Xuan Zhuo wrote:
> @@ -532,9 +545,9 @@ struct xdp_buff *xp_alloc(struct xsk_buff_pool *pool)
>  	xskb->xdp.data_meta = xskb->xdp.data;
>  
>  	if (pool->dma_need_sync) {
> -		dma_sync_single_range_for_device(pool->dev, xskb->dma, 0,
> -						 pool->frame_len,
> -						 DMA_BIDIRECTIONAL);
> +		pool->dma_ops.sync_single_range_for_device(pool->dev, xskb->dma, 0,
> +							   pool->frame_len,
> +							   DMA_BIDIRECTIONAL);
>  	}
>  	return &xskb->xdp;
>  }
> @@ -670,15 +683,15 @@ EXPORT_SYMBOL(xp_raw_get_dma);
>  
>  void xp_dma_sync_for_cpu_slow(struct xdp_buff_xsk *xskb)
>  {
> -	dma_sync_single_range_for_cpu(xskb->pool->dev, xskb->dma, 0,
> -				      xskb->pool->frame_len, DMA_BIDIRECTIONAL);
> +	xskb->pool->dma_ops.sync_single_range_for_cpu(xskb->pool->dev, xskb->dma, 0,
> +						      xskb->pool->frame_len, DMA_BIDIRECTIONAL);
>  }
>  EXPORT_SYMBOL(xp_dma_sync_for_cpu_slow);
>  
>  void xp_dma_sync_for_device_slow(struct xsk_buff_pool *pool, dma_addr_t dma,
>  				 size_t size)
>  {
> -	dma_sync_single_range_for_device(pool->dev, dma, 0,
> -					 size, DMA_BIDIRECTIONAL);
> +	pool->dma_ops.sync_single_range_for_device(pool->dev, dma, 0,
> +						   size, DMA_BIDIRECTIONAL);
>  }
>  EXPORT_SYMBOL(xp_dma_sync_for_device_slow);

So you add an indirect function call on data path? Won't this be costly?

> -- 
> 2.32.0.3.g01195cf9f


  parent reply	other threads:[~2023-04-17  6:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  3:27 [PATCH net-next] xsk: introduce xsk_dma_ops Xuan Zhuo
2023-04-17  4:24 ` Christoph Hellwig
2023-04-17  5:58   ` Xuan Zhuo
2023-04-17 18:56     ` Jakub Kicinski
2023-04-17 18:57       ` Jakub Kicinski
2023-04-18  1:07         ` Jason Wang
2023-04-18  1:19           ` Jakub Kicinski
2023-04-18  2:19             ` Xuan Zhuo
2023-04-18  2:54               ` Jakub Kicinski
2023-04-18  5:01                 ` Christoph Hellwig
2023-04-18  6:19                   ` Jakub Kicinski
2023-04-19  5:16                     ` Christoph Hellwig
2023-04-19 13:14                       ` Alexander Lobakin
2023-04-19 13:40                         ` Xuan Zhuo
2023-04-20  6:16                         ` Christoph Hellwig
2023-04-20 13:59                           ` Alexander Lobakin
2023-04-20 16:15                             ` Christoph Hellwig
2023-04-20 16:42                               ` Alexander Lobakin
2023-05-01  4:28                                 ` Christoph Hellwig
2023-04-19 16:45                       ` Jakub Kicinski
2023-04-20  6:19                         ` Christoph Hellwig
2023-04-20  9:11                           ` Xuan Zhuo
2023-04-20 16:18                             ` Christoph Hellwig
2023-04-25  8:12                               ` Michael S. Tsirkin
2023-05-01  4:16                                 ` Christoph Hellwig
2023-04-20 14:13                           ` Jakub Kicinski
2023-04-21  7:31                             ` Xuan Zhuo
2023-04-21 13:50                               ` Jakub Kicinski
2023-04-23  1:54                                 ` Xuan Zhuo
2023-04-24 15:28                                   ` Jakub Kicinski
2023-04-24 15:28                                 ` Alexander Lobakin
2023-04-25  2:11                                   ` Xuan Zhuo
2023-04-18  2:15         ` Xuan Zhuo
2023-04-17  6:38 ` kernel test robot
2023-04-17  6:43 ` Michael S. Tsirkin [this message]
2023-04-17  6:48   ` Xuan Zhuo
2023-04-17  6:48 ` kernel test robot
2023-04-19 13:22 ` Alexander Lobakin
2023-04-19 13:42   ` Xuan Zhuo
2023-04-20  6:12   ` Christoph Hellwig

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=20230417024216-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux@roeck-us.net \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xuanzhuo@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).