Prev: [PATCH 4/5] perf, x86: Clear the LBRs on init
Next: [PATCH 4/6] perf session: Add storage for seperating event types in report
From: David Miller on 5 Mar 2010 13:10
From: Jesse Barnes <jbarnes(a)virtuousgeek.org>
Date: Fri, 5 Mar 2010 10:02:44 -0800

> So from that perspective, the graphics stack is the most complex one in
> Linux by a long shot. It's even worse than if we had STREAMS
> networking with a ton of different modules up in userspace messing with
> protocol. :)

Maybe :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Xavier Bestel on 5 Mar 2010 13:20
On Fri, 2010-03-05 at 07:49 -0800, David Miller wrote:
> From: Daniel Stone <daniel(a)fooishbar.org>
> Date: Fri, 5 Mar 2010 17:41:43 +0200
>
> > I understand that you guys are upset about this, so maybe you'd like to
> > donate, say, 10% of your developer base to help out? That'd be pretty
> > ace.
>
> You have to support less than %10 of the amount of hardware we have to
> support.

You can't compare a network card and a GPU. The latter is way more
complex to code for.

Xav

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: [PATCH 4/5] perf, x86: Clear the LBRs on init
Next: [PATCH 4/6] perf session: Add storage for seperating event types in report