On Tue, Feb 18, 2025 at 11:31:54AM -0400, Jason Gunthorpe wrote:
> On Fri, Jan 24, 2025 at 04:30:35PM -0800, Nicolin Chen wrote:
> > This is a reverse search v.s. iommufd_viommu_find_dev, as drivers may want
> > to convert a struct device pointer (physical) to its virtual device ID for
> > an event
On 2/17/25 23:26, Mina Almasry wrote:
On Thu, Feb 13, 2025 at 5:17 AM Pavel Begunkov wrote:
...
It's asserting that sizeof(ubuf_info_msgzc) <= sizeof(skb->cb), and
I'm guessing increasing skb->cb size is not really the way to go.
What I may be able to do here is stash the binding somewhere in
On Wed, Feb 19, 2025 at 3:41 PM Rasmus Villemoes
wrote:
>
> On Fri, 14 Feb 2025 at 22:53, Tamir Duberstein wrote:
> >
> > This improves the failure output by pointing to the failing line at the
> > top level of the test, e.g.:
> > # test_number: EXPECTATION FAILED at lib/printf_kunit.c:103
v4:
https://lore.kernel.org/netdev/20250203223916.1064540-1-almasrym...@google.com/
===
v4 mainly addresses the critical driver support issue surfaced in v3 by
Paolo and Stan. Drivers aiming to support netmem_tx should make sure not
to pass the netmem dma-addrs to the dma-mapping APIs, as these d
Currently net_iovs support only pp ref counts, and do not support a
page ref equivalent.
This is fine for the RX path as net_iovs are used exclusively with the
pp and only pp refcounting is needed there. The TX path however does not
use pp ref counts, thus, support for get_page/put_page equivalent
From: Stanislav Fomichev
Add bind-tx netlink call to attach dmabuf for TX; queue is not
required, only ifindex and dmabuf fd for attachment.
Signed-off-by: Stanislav Fomichev
Signed-off-by: Mina Almasry
---
v3:
- Fix ynl-regen.sh error (Simon).
---
Documentation/netlink/specs/netdev.yaml |
Add documentation outlining the usage and details of the devmem TCP TX
API.
Signed-off-by: Mina Almasry
---
v4:
- Mention SO_BINDTODEVICE is recommended (me/Pavel).
v2:
- Update documentation for iov_base is the dmabuf offset (Stan)
---
Documentation/networking/devmem.rst | 150 +
Augment dmabuf binding to be able to handle TX. Additional to all the RX
binding, we also create tx_vec needed for the TX path.
Provide API for sendmsg to be able to send dmabufs bound to this device:
- Provide a new dmabuf_tx_cmsg which includes the dmabuf to send from.
- MSG_ZEROCOPY with SCM_D
The TX path may release the dmabuf in a context where we cannot wait.
This happens when the user unbinds a TX dmabuf while there are still
references to its netmems in the TX path. In that case, the netmems will
be put_netmem'd from a context where we can't unmap the dmabuf,
resulting in a BUG like
Drivers need to make sure not to pass netmem dma-addrs to the
dma-mapping API in order to support netmem TX.
Add helpers and netmem_dma_*() helpers that enables special handling of
netmem dma-addrs that drivers can use.
Document in netmem.rst what drivers need to do to support netmem TX.
Signed-
We should not enable netmem TX for drivers that don't declare support.
Check for driver netmem TX support during devmem TX binding and fail if
the driver does not have the functionality.
Check for driver support in validate_xmit_skb as well.
Signed-off-by: Mina Almasry
---
v4:
- New patch
--
Add support for devmem TX in ncdevmem.
This is a combination of the ncdevmem from the devmem TCP series RFCv1
which included the TX path, and work by Stan to include the netlink API
and refactored on top of his generic memory_provider support.
Signed-off-by: Mina Almasry
Signed-off-by: Stanislav
Use netmem_dma_*() helpers in gve_tx_dqo.c DQO-RDA paths to
enable netmem TX support in that mode.
Declare support for netmem TX in GVE DQO-RDA mode.
Signed-off-by: Mina Almasry
---
v4:
- New patch
---
drivers/net/ethernet/google/gve/gve_main.c | 4
drivers/net/ethernet/google/gve/gve_
On Fri, 14 Feb 2025 at 22:53, Tamir Duberstein wrote:
>
> This improves the failure output by pointing to the failing line at the
> top level of the test, e.g.:
> # test_number: EXPECTATION FAILED at lib/printf_kunit.c:103
> lib/printf_kunit.c:167: vsnprintf(buf, 256, "%#-12x", ...) wrote
On Wed, Feb 19, 2025 at 2:40 PM Pavel Begunkov wrote:
>
> On 2/17/25 23:26, Mina Almasry wrote:
> > On Thu, Feb 13, 2025 at 5:17 AM Pavel Begunkov
> > wrote:
> ...
> > It's asserting that sizeof(ubuf_info_msgzc) <= sizeof(skb->cb), and
> > I'm guessing increasing skb->cb size is not real
Hi,
On 2/15/25 7:04 AM, Akihiko Odaki wrote:
> tun simply advances iov_iter when it needs to pad virtio header,
> which leaves the garbage in the buffer as is. This will become
> especially problematic when tun starts to allow enabling the hash
> reporting feature; even if the feature is enabled,
On Tue, Feb 18, 2025 at 02:52:29PM -0400, Jason Gunthorpe wrote:
> On Tue, Feb 18, 2025 at 06:17:15PM +, Pranjal Shrivastava wrote:
>
> > > Is MEV available only in nested mode? Otherwise it perhaps makes
> > > sense to turn it on in all configurations in IOMMUFD paths...
> >
> > I think the
On Tue, Feb 18, 2025 at 01:08:24PM -0400, Jason Gunthorpe wrote:
> On Fri, Jan 24, 2025 at 04:30:41PM -0800, Nicolin Chen wrote:
> > + int ret;
> > struct arm_smmu_ste ste;
> > struct arm_smmu_master *master = dev_iommu_priv_get(dev);
> > + struct arm_smmu_attach_state state = {
> > +
In preparation for letting kerneldoc Sphinx extension to import
Python libraries, move regex ancillary classes to a separate
file.
Signed-off-by: Mauro Carvalho Chehab
---
scripts/kernel-doc.py | 1634 +-
scripts/lib/kdoc/kdoc_parser.py | 1689 ++
Hi Jon,
This changeset contains the kernel-doc.py script to replace the verable
kernel-doc originally written in Perl.
As the previous versions, I tried to stay as close as possible of the original
Perl implementation, as it helps to double check if each function was
properly translated to Pytho
Maintaining kernel-doc has been a challenge, as there aren't many
perl developers among maintainers. Also, the logic there is too
complex. Having lots of global variables and using pure functions
doesn't help.
Rewrite the script in Python, placing most global variables
inside classes. This should
On 2/11/2025 9:14 PM, Andrew Lunn wrote:
+/* Assign the share buffer number 1550 to group 0 by default. */
+static const int ipq9574_ppe_bm_group_config = 1550;
To a large extent, the comment is useless. What should be in the
comment is why, not what.
Andrew
OK, I will improve th
On Feb 18, 2025, at 08:50, Wei Yang wrote:
>
> This patch adjust the example code with following two purpose:
>
> * reduce the confusion on not releasing e->lock
> * emphasize e is valid and not stale with e->lock held
>
> Signed-off-by: Wei Yang
> CC: Boqun Feng
> CC: Alan Huang
>
> ---
On Tue, Feb 18, 2025 at 12:50:47AM +, Wei Yang wrote:
> This patch adjust the example code with following two purpose:
>
> * reduce the confusion on not releasing e->lock
> * emphasize e is valid and not stale with e->lock held
>
> Signed-off-by: Wei Yang
> CC: Boqun Feng
> CC: Alan Hua
24 matches
Mail list logo
