public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
	asml.silence@gmail.com, Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	Simona Vetter <simona.vetter@ffwll.ch>,
	Willem de Bruijn <willemb@google.com>,
	Kaiyuan Zhang <kaiyuanz@google.com>,
	cratiu@nvidia.com, parav@nvidia.com,
	Tariq Toukan <tariqt@nvidia.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	io-uring@vger.kernel.org
Subject: Re: [PATCH net] net: Allow non parent devices to be used for ZC DMA
Date: Thu, 10 Jul 2025 16:47:29 -0700	[thread overview]
Message-ID: <20250710164729.275f62fd@kernel.org> (raw)
In-Reply-To: <CAHS8izP18q7s8=fGCjknrEu3uJE5xnQCKceB8u1VvTV5GxTTTg@mail.gmail.com>

On Wed, 9 Jul 2025 15:56:16 -0700 Mina Almasry wrote:
> > > nit: This doesn't seem like a fix? The current code supports all
> > > devices that are not SF well enough, right? And in the case of SF
> > > devices, I expect net_devmem_bind_dmabuf() to fail gracefully as the
> > > dma mapping of a device that doesn't support it, I think, would fail
> > > gracefully. So to me this seems like an improvement rather than a bug
> > > fix.
> > >  
> > dma_buf_map_attachment_unlocked() will return a sg_table with 0 nents.
> > That is graceful. However this will result in page_pools that will
> > always be returning errors further down the line which is very confusing
> > regarding the motives that caused it.
> >
> > I am also fine to not make it a fix btw. Especially since the mlx5
> > devmem code was just accepted.
> 
> If you submit another version I'd rather it be a non-fix, especially
> since applying the io_uring hunk will be challenging when backporting
> this patch, but I assume hunk can be dropped while backporting, so I'm
> fine either way.

+1 for non-fix. The core is working as expected, if we want a Fixes tag
I'd aim it at mlx5 and make the patch reject queue binding to SFs
_within mlx5_ until the core bits are figured out.

  reply	other threads:[~2025-07-10 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 12:40 [PATCH net] net: Allow non parent devices to be used for ZC DMA Dragos Tatulea
2025-07-09 13:50 ` Pavel Begunkov
2025-07-09 19:29 ` Mina Almasry
2025-07-09 19:53   ` Dragos Tatulea
2025-07-09 22:56     ` Mina Almasry
2025-07-10 23:47       ` Jakub Kicinski [this message]
2025-07-10 23:49 ` 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=20250710164729.275f62fd@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=kaiyuanz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=tariqt@nvidia.com \
    --cc=willemb@google.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