linux-kernel - Re: [PATCH -mm 0/3] convert IOMMUs to use iova

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071102171227.GH7975@rhun.haifa.ibm.com>
Date:	Fri, 2 Nov 2007 19:12:27 +0200
From:	Muli Ben-Yehuda <muli@...ibm.com>
To:	FUJITA Tomonori <tomof@....org>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	James.Bottomley@...elEye.com, jens.axboe@...cle.com,
	jeff@...zik.org, anil.s.keshavamurthy@...el.com, paulus@...ba.org,
	anton@...ba.org, olof@...om.net, tony.luck@...el.com,
	davem@...emloft.net, kyle@...isc-linux.org,
	fujita.tomonori@....ntt.co.jp
Subject: Re: [PATCH -mm 0/3] convert IOMMUs to use iova

On Sat, Nov 03, 2007 at 02:05:39AM +0900, FUJITA Tomonori wrote:

> This patchset convert the PPC64 IOMMU to use the iova code for free
> area management.
> 
> The IOMMUs ignores low level drivers' restrictions, the maximum
> segment size and segment boundary.
> 
> I fixed the former:
> 
> http://thread.gmane.org/gmane.linux.scsi/35602
> 
> The latter makes the free area management complicated. I'd like to
> convert IOMMUs to use the iova code (that intel-iommu introduced)
> for free area management and enable iova to handle segment boundary
> restrictions, rather than fixing all the IOMMUs' free area
> management,

In general it sounds like a great idea, but have you looked at what
impact this has on the performance of the IO path?

Cheers,
Muli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/