> Date: Tue, 11 Jun 2019 11:51:51 +1000
> From: David Gwynne
>
> this is a reposting of the diff i sent out a while back. it lets sparc64
> enable iommu bypass, and then uses that bypass support for BUS_DMA_64BIT
> dmamaps.
>
> the main benefit is around performance. without this diff on an
Upgraded my T5240 using the latest bsd.rd, all is fine - no noticable
regression in production.
This is great, thanks for the work. I have the new snapshot running on
a T5220. I also have an Ultra 45 with some GPUs I use mainly for
playing games and sending people bug reports about how their game
doesn't work on sparc64, I'll try it there also. If there are any
specific tests you want done,
I'm mostly concerned that nothing that currently works breaks. This changes a
fairly fundamental chunk of code in the guts of the platform, so having
machines still work afterward would be nice.
Glad your T5220 works, hopefully the u45 will be ok too.
dlg
> On 20 Jun 2019, at 08:52, Kaashif
I have the snapshot running on a guest domain on a T1000 - see attached.
I will test on the primary in a few days, and may be able to test on a
T5220 primary towards the end of next week.
Let me know if you want any specific test procedure run.
On Tue, 18 Jun 2019 at 02:37, Theo de Raadt
David Gwynne wrote:
> this is a reposting of the diff i sent out a while back. it lets sparc64
> enable iommu bypass, and then uses that bypass support for BUS_DMA_64BIT
> dmamaps.
BTW, this is in snapshots and I'd urge everyone running sparc64 to give it
a try.
this is a reposting of the diff i sent out a while back. it lets sparc64
enable iommu bypass, and then uses that bypass support for BUS_DMA_64BIT
dmamaps.
the main benefit is around performance. without this diff on an M4000,
tcpbench can do about 70Mbps before the system is CPU bound. all that
