From: Michael Ellerman <mpe@ellerman.id.au>
To: Gaurav Batra <gbatra@linux.vnet.ibm.com>
Cc: Brian King <brking@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Greg Joyce <gjoyce@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] powerpc/iommu: DMA address offset is incorrectly calculated with 2MB TCEs
Date: Thu, 04 May 2023 15:10:14 +1000 [thread overview]
Message-ID: <87354c8yx5.fsf@mail.lhotse> (raw)
In-Reply-To: <1ce16c05-b492-fed8-06af-0bbba9de9053@linux.vnet.ibm.com>
Gaurav Batra <gbatra@linux.vnet.ibm.com> writes:
> Hello Michael,
>
> I was looking into the Bug: 199106
> (https://bugzilla.linux.ibm.com/show_bug.cgi?id=199106).
>
> In the Bug, Mellanox driver was timing out when enabling SRIOV device.
>
> I tested, Alexey's patch and it fixes the issue with Mellanox driver.
> The down side
>
> to Alexey's fix is that even a small memory request by the driver will
> be aligned up
>
> to 2MB. In my test, the Mellanox driver is issuing multiple requests of
> 64K size.
>
> All these will get aligned up to 2MB, which is quite a waste of resources.
OK. I guess we should use your patch then.
It's not ideal as it means the device can potentially read/write to
memory it shouldn't, but 2MB is a lot to waste for a 64K alloc.
> In any case, both the patches work. Let me know which approach you
> prefer. In case
>
> we decide to go with my patch, I just realized that I need to fix
> nio_pages in
>
> iommu_free_coherent() as well.
Can you send a v3 with that fixed please.
cheers
next prev parent reply other threads:[~2023-05-04 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 15:26 [PATCH v2] powerpc/iommu: DMA address offset is incorrectly calculated with 2MB TCEs Gaurav Batra
2023-04-20 15:21 ` Michael Ellerman
2023-04-20 19:45 ` Gaurav Batra
2023-05-03 3:25 ` Gaurav Batra
2023-05-22 0:08 ` Alexey Kardashevskiy
2023-05-22 13:11 ` Gaurav Batra
2023-05-04 5:10 ` Michael Ellerman [this message]
2023-05-04 18:03 ` Gaurav Batra
2023-05-05 2:21 ` Michael Ellerman
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=87354c8yx5.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=brking@linux.vnet.ibm.com \
--cc=gbatra@linux.vnet.ibm.com \
--cc=gjoyce@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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 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).