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]
Date:	Tue, 24 Aug 2010 13:44:27 -0500
From:	"Guzman Lugo, Fernando" <fernando.lugo@...com>
To:	Felipe Contreras <felipe.contreras@...il.com>
CC:	"Kanigeri, Hari" <h-kanigeri2@...com>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ohad@...ery.com" <ohad@...ery.com>,
	"hiroshi.doyu@...ia.com" <hiroshi.doyu@...ia.com>,
	"ameya.palande@...ia.com" <ameya.palande@...ia.com>,
	"felipe.contreras@...ia.com" <felipe.contreras@...ia.com>
Subject: RE: [PATCH 8/9] dspbridge: add map support for big buffers

 

> -----Original Message-----
> From: Felipe Contreras [mailto:felipe.contreras@...il.com] 
> Sent: Tuesday, August 24, 2010 12:46 PM
> To: Guzman Lugo, Fernando
> Cc: Kanigeri, Hari; linux-omap@...r.kernel.org; 
> linux-kernel@...r.kernel.org; ohad@...ery.com; 
> hiroshi.doyu@...ia.com; ameya.palande@...ia.com; 
> felipe.contreras@...ia.com
> Subject: Re: [PATCH 8/9] dspbridge: add map support for big buffers
> 
> On Tue, Aug 24, 2010 at 7:31 PM, Guzman Lugo, Fernando 
> <fernando.lugo@...com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Felipe Contreras [mailto:felipe.contreras@...il.com]
> >> Sent: Tuesday, August 24, 2010 5:09 AM
> >> To: Guzman Lugo, Fernando
> >> Cc: Kanigeri, Hari; linux-omap@...r.kernel.org; 
> >> linux-kernel@...r.kernel.org; ohad@...ery.com; 
> >> hiroshi.doyu@...ia.com; ameya.palande@...ia.com; 
> >> felipe.contreras@...ia.com
> >> Subject: Re: [PATCH 8/9] dspbridge: add map support for big buffers
> >>
> >> On Fri, Jul 2, 2010 at 9:39 PM, Guzman Lugo, Fernando 
> >> <fernando.lugo@...com> wrote:
> >> > I think, it would be good if we get rid of DMMPOOL size, if
> >> the liked list grow up as it is needed, there is no memory 
> penalty of 
> >> have all the possible iommu addresses valid (11000000 - FFFFFFFF). 
> >> The reservation will only fail when there is no memory. If 
> a software 
> >> restriction is needed we could define a start and end 
> addresses for 
> >> iommu module (maybe as a parameter when the iommu handle 
> for iva2 is 
> >> got) and that boundaries can be taking in account at the moment of 
> >> reserve the memory.
> >>
> >> What happened to this?
> >>
> >> IIUC what you are proposing is to remove the DMM pool completely, 
> >> that makes sense to me. However, is it really needed to finish the 
> >> iommu migration to do this?
> >>
> >> > I think the reserve/unreserved dspbridge api can disappear
> >> and just return the da address in the map function.
> >>
> >> This is something I've proposed before, so I agree :)
> >
> > Yeah, that is how it will be. I have been busy with other 
> stuffs, but 
> > now I have finish a version with all dmm module removed and 
> > reserve/unreserve Api removed as well. But because a the big # of 
> > patches merge in dspbrdge I have to rebase them to the 
> latest, I hope 
> > finish this week and send Them again next week.
> 
> Awesome :)
> 
> However, I still have the question about the dependency on 
> iommu; AFAICS the DMM removal doesn't depend on the migration 
> to iommu, which AFAIK has been stalled for some time.

Yeah, DMM removal does not depend on iommu migration. However,
After the changes for iommu migration the DMM module is not
Needed anymore, so it is better to remove it too.


Regards,
Fernando.

> 
> --
> Felipe Contreras
> --
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ