From: Jason Gunthorpe <jgg@ziepe.ca>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux.dev, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
Rob Clark <robdclark@gmail.com>,
Gaurav Kohli <quic_gkohli@quicinc.com>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH v2 0/2] iommu: Allow passing custom allocators to pgtable drivers
Date: Mon, 20 Nov 2023 10:04:25 -0400 [thread overview]
Message-ID: <20231120140425.GA10140@ziepe.ca> (raw)
In-Reply-To: <ZVOgBBEetWf1PFxX@nvidia.com>
On Tue, Nov 14, 2023 at 12:27:48PM -0400, Jason Gunthorpe wrote:
> > Anyway, given you already thought it through, can I ask you to provide
> > a preliminary implementation for this IOVA range mechanism so I can
> > play with it and adjust panthor accordingly. And if you don't have the
> > time, can you at least give me extra details about the implementation
> > you had in mind, so I don't have to guess and come back with something
> > that's not matching what you had in mind.
>
> Oh, I don't know if I can manage patches in any reasonable time frame,
> though I think it is pretty straightforward really:
>
> - Patch to introduce some 'struct iopte_page' (see struct slab)
> - Adjust io pagetable implementations to consume it
> - Do RCU freeing of iopte_page
> - Add a reserve/unreserve io page table ops
> - Implement reserve/unresereve in arm by manipulating a new refcount
> in iopte_page. Rely on RCU to protect the derefs
> - Modify iommufd to call reserve/unreserve around areas attachment
> to have an intree user.
>
> Some of this is a bit interesting, like reserving probably will
> ideally want to invoke the batch allocator for efficiency which means
> computing the number of radix levels required to fully populate the
> current empty level - that should be general code somehow
At LPC there was quite a lot if interest in improving the io page
table stuff to work better. Based on that I'm even more against adding
an external allocator at this time. :\
I may try to write a sketch of something but I'm not sure when..
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux.dev, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
Rob Clark <robdclark@gmail.com>,
Gaurav Kohli <quic_gkohli@quicinc.com>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH v2 0/2] iommu: Allow passing custom allocators to pgtable drivers
Date: Mon, 20 Nov 2023 10:04:25 -0400 [thread overview]
Message-ID: <20231120140425.GA10140@ziepe.ca> (raw)
In-Reply-To: <ZVOgBBEetWf1PFxX@nvidia.com>
On Tue, Nov 14, 2023 at 12:27:48PM -0400, Jason Gunthorpe wrote:
> > Anyway, given you already thought it through, can I ask you to provide
> > a preliminary implementation for this IOVA range mechanism so I can
> > play with it and adjust panthor accordingly. And if you don't have the
> > time, can you at least give me extra details about the implementation
> > you had in mind, so I don't have to guess and come back with something
> > that's not matching what you had in mind.
>
> Oh, I don't know if I can manage patches in any reasonable time frame,
> though I think it is pretty straightforward really:
>
> - Patch to introduce some 'struct iopte_page' (see struct slab)
> - Adjust io pagetable implementations to consume it
> - Do RCU freeing of iopte_page
> - Add a reserve/unreserve io page table ops
> - Implement reserve/unresereve in arm by manipulating a new refcount
> in iopte_page. Rely on RCU to protect the derefs
> - Modify iommufd to call reserve/unreserve around areas attachment
> to have an intree user.
>
> Some of this is a bit interesting, like reserving probably will
> ideally want to invoke the batch allocator for efficiency which means
> computing the number of radix levels required to fully populate the
> current empty level - that should be general code somehow
At LPC there was quite a lot if interest in improving the io page
table stuff to work better. Based on that I'm even more against adding
an external allocator at this time. :\
I may try to write a sketch of something but I'm not sure when..
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-20 14:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:43 [PATCH v2 0/2] iommu: Allow passing custom allocators to pgtable drivers Boris Brezillon
2023-11-10 9:43 ` Boris Brezillon
2023-11-10 9:43 ` [PATCH v2 1/2] " Boris Brezillon
2023-11-10 9:43 ` Boris Brezillon
2023-11-22 13:08 ` Robin Murphy
2023-11-22 13:08 ` Robin Murphy
2023-11-10 9:43 ` [PATCH v2 2/2] iommu: Extend LPAE page table format to support custom allocators Boris Brezillon
2023-11-10 9:43 ` Boris Brezillon
2023-11-22 14:24 ` Robin Murphy
2023-11-22 14:24 ` Robin Murphy
2023-11-10 10:47 ` [PATCH v2 0/2] iommu: Allow passing custom allocators to pgtable drivers Gaurav Kohli
2023-11-10 10:47 ` Gaurav Kohli
2023-11-10 15:14 ` Jason Gunthorpe
2023-11-10 15:14 ` Jason Gunthorpe
2023-11-10 15:48 ` Boris Brezillon
2023-11-10 15:48 ` Boris Brezillon
2023-11-10 16:12 ` Jason Gunthorpe
2023-11-10 16:12 ` Jason Gunthorpe
2023-11-10 19:16 ` Boris Brezillon
2023-11-10 19:16 ` Boris Brezillon
2023-11-10 19:42 ` Jason Gunthorpe
2023-11-10 19:42 ` Jason Gunthorpe
2023-11-13 9:11 ` Boris Brezillon
2023-11-13 9:11 ` Boris Brezillon
2023-11-14 16:27 ` Jason Gunthorpe
2023-11-14 16:27 ` Jason Gunthorpe
2023-11-20 14:04 ` Jason Gunthorpe [this message]
2023-11-20 14:04 ` Jason Gunthorpe
2023-11-20 14:38 ` Boris Brezillon
2023-11-20 14:38 ` Boris Brezillon
2023-11-20 14:46 ` Jason Gunthorpe
2023-11-20 14:46 ` Jason Gunthorpe
2023-11-20 15:14 ` Boris Brezillon
2023-11-20 15:14 ` Boris Brezillon
2023-11-20 15:45 ` Jason Gunthorpe
2023-11-20 15:45 ` Jason Gunthorpe
2023-11-22 17:23 ` Robin Murphy
2023-11-22 17:23 ` Robin Murphy
2023-11-22 17:50 ` Jason Gunthorpe
2023-11-22 17:50 ` Jason Gunthorpe
2023-11-23 8:51 ` Boris Brezillon
2023-11-23 8:51 ` Boris Brezillon
2023-11-23 13:48 ` Jason Gunthorpe
2023-11-23 13:48 ` Jason Gunthorpe
2023-11-23 16:49 ` Robin Murphy
2023-11-23 16:49 ` Robin Murphy
2023-11-23 16:59 ` Jason Gunthorpe
2023-11-23 16:59 ` Jason Gunthorpe
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=20231120140425.GA10140@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=boris.brezillon@collabora.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=quic_gkohli@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
/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.