[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zu1wim6MZz3rkbWY@ziepe.ca>
Date: Fri, 20 Sep 2024 09:54:34 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Baolu Lu <baolu.lu@...ux.intel.com>
Cc: "Tian, Kevin" <kevin.tian@...el.com>,
"j.granados@...sung.com" <j.granados@...sung.com>,
David Woodhouse <dwmw2@...radead.org>,
Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Klaus Jensen <its@...elevant.dk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>
Subject: Re: [PATCH v2 1/5] iommu/vt-d: Separate page request queue from SVM
On Wed, Sep 18, 2024 at 07:17:32PM +0800, Baolu Lu wrote:
> > more than that... for each IOMMU the current code allocates 16 pages
> > and 1 hwirq. Those are unnecessary burdens in majority deployments
> > which don't support/require I/O page faults.
>
> Yeah! I only focused on the kernel binary size but ignored these system
> resources consumed by IOPF. Then, perhaps
If you care about runtime overhead it should be delt with by
dynamically allocating the memory and enabling it, not via kconfig
We can dynmaically add IRQS in some cases now for instance
Jason
Powered by blists - more mailing lists