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:	Mon, 30 Jul 2007 10:51:17 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Matthew Hawkins <darthmdh@...il.com>
Cc:	Jacob Braun <jwbraun@...il.com>, kriko <kristjan.ugrin@...il.com>,
	ck@....kolivas.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-mm@...ck.org, Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [ck] Re: SD still better than CFS for 3d ?(was Re: 2.6.23-rc1)

On Tue, 2007-07-31 at 02:25 +1000, Matthew Hawkins wrote:
> On 7/31/07, Jacob Braun <jwbraun@...il.com> wrote:
> > On 7/30/07, kriko <kristjan.ugrin@...il.com> wrote:
> > > I would try the new cfs how it performs, but it seems that nvidia drivers
> > > doesn't compile successfully under 2.6.23-rc1.
> > > http://files.myopera.com/kriko/files/nvidia-installer.log
> > >
> > > If someone has the solution, please share.
> >
> > There is a patch for the nvidia drivers here:
> > http://bugs.gentoo.org/attachment.cgi?id=125959
> 
> The ATI drivers (current 8.39.4) were broken by
> commit e21ea246bce5bb93dd822de420172ec280aed492
> Author: Martin Schwidefsky <schwidefsky@...ibm.com>


some fo these binary drivers do really really bad stuff (esp the AMD
ones are infamous for that) and it's no surprise they might throw of a
new scheduler. In fact, that's a bonus, some of those hacks are
workarounds for older (often 2.4) scheduler corner cases and should just
be removed from the driver to get better performance. Holding back linux
for such hacky junk in binary drivers would be the absolute worst thing
to do; even for people who insist on using these drivers over the open
source ones, since the next rev of these drivers can now use the new
scheduler and actually be faster with all the workarounds removed.

Very likely the best thing to do is to contact the supplier of the
driver (AMD or Nvidia) and ask them to fix it.....



-
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