public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>, Frans Pop <elendil@planet.nl>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Unable to continue testing of 2.6.25
Date: Mon, 18 Feb 2008 19:52:28 +0100	[thread overview]
Message-ID: <20080218185228.GA29026@one.firstfloor.org> (raw)
In-Reply-To: <20080218093215.5cf611a8@laptopd505.fenrus.org>

> I've yet to see a user who wants WC. Lets face it, WC *sucks*. This is why

Interesting.
 
> the folks who care about performance (the graphics guys) stopped using it.

I didn't know this. What do they do instead?

I understand that WC was added originally because AGP was really slow
at IO towards the CPU. You mean on PCI-E it is fast enough now
that standard cached WB works well enough?

> WC is slow, and on modern cpus leads to really bad performance. I'm really
> half tempted to just ignore WC entirely and suggest that we don't even implement
> it in the kernel. Yes it's really that bad.

At least the X server still uses it. In fact there are already some
performance regression regarding this from differing kernel behavioun
in the sysfs interfaces vs /dev/mem.

What would you recommend should the X server use instead? Always
map standard WB?  How about on older AGP systems?

-Andi


  parent reply	other threads:[~2008-02-18 18:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  9:25 Unable to continue testing of 2.6.25 Frans Pop
2008-02-17 13:16 ` Adrian Bunk
2008-02-17 19:24   ` Tilman Schmidt
2008-02-17 19:44     ` Adrian Bunk
2008-02-17 20:38       ` Paul Jackson
2008-02-17 20:51         ` Arjan van de Ven
2008-02-19 22:41           ` Frans Pop
2008-02-18  2:33     ` David Miller
2008-02-18 11:40       ` Tilman Schmidt
2008-02-18 12:27       ` Andi Kleen
2008-02-19 21:55   ` Frans Pop
2008-02-19 21:59     ` Arjan van de Ven
2008-02-19 22:15     ` Harvey Harrison
2008-02-19 22:19     ` Adrian Bunk
2008-02-19 22:49       ` Frans Pop
2008-02-17 20:46 ` Arjan van de Ven
2008-02-18 12:31   ` Andi Kleen
2008-02-18 16:50     ` Arjan van de Ven
2008-02-18 17:11       ` Andi Kleen
2008-02-18 17:32         ` Arjan van de Ven
2008-02-18 18:40           ` Alan Cox
2008-02-18 18:52             ` Arjan van de Ven
2008-02-18 20:15               ` Alan Cox
2008-02-18 18:52           ` Andi Kleen [this message]
2008-02-18 18:32             ` Arjan van de Ven
2008-02-18 19:18             ` Ingo Molnar
2008-02-19  9:35               ` Andi Kleen
2008-02-18 18:53           ` Roland Dreier
2008-02-18 19:07             ` Arjan van de Ven
2008-02-18 19:18               ` Roland Dreier
2008-02-19 19:42                 ` Siddha, Suresh B

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080218185228.GA29026@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox