| 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
| ||
|
Date: Fri, 21 Dec 2007 13:28:26 +1100 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Richard Henderson <rth@...ddle.net>, Chuck Ebbert <cebbert@...hat.com>, linux-kernel <linux-kernel@...r.kernel.org>, Ivan Kokshaysky <ink@...assic.park.msu.ru>, Daniel Ritz <daniel.ritz@....ch>, Greg KH <greg@...ah.com>, Keith Packard <keithp@...thp.com>, Bjorn Helgaas <bjorn.helgaas@...com> Subject: Re: PCI resource problems caused by improper address rounding > So in your case, it should *result* in the exact same situation that your > patch did, but at the same time, when dealing with the (more common) case > of smaller allocations, we still continue to try to avoid being too close > to the top-of-memory. > > So it's not perfect, but perhaps it is a good compromise between being > careful and having to make room? > > Does this work for your case? I'm not totally happy with changing the generic code like that, to possibly not enforce "min" anymore. Other archs may have very good reasons to provide a min value here... Though at the same time, at least on powerpc, the parent resource of the host bridge will be the real limit, so that may not be a big issue. Cheers, Ben. -- 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