All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: geert@linux-m68k.org (Geert Uytterhoeven),
	jsimmons@linux-fbdev.org (James Simmons),
	lk@tantalophile.demon.co.uk (Jamie Lokier),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
	linux-fbdev-devel@lists.sourceforge.net (Linux Fbdev development
	list)
Subject: Re: [Linux-fbdev-devel] Re: fbcon slowness [was NTP on 2.4.2?]
Date: 04 Apr 2001 01:50:41 -0600	[thread overview]
Message-ID: <m1lmphw1bi.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E14kPoq-0007w5-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Tue, 3 Apr 2001 13:21:53 +0100 (BST)"

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> > > The MMX memcpy for CyrixIII and Athlon boxes is something like twice the
> > > speed of rep movs. On most pentium II/III boxes the fast paths for rep movs
> > > and for MMX are the same speed
> > 
> > As long as you are copying in real memory. So the PCI bus or the host bridge
> > implementation may be the actual limit.
> 
> The CyrixIII sits on the same host bridges as the intel processors

I don't know if it applies to this case but one thing I have seen make
a noticeable difference is whether or not write-combining is enabled.
If we have only be enabling MTRR's for intel this could do account
for it.

Eric

  reply	other threads:[~2001-04-04  7:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31  4:11 [Linux-fbdev-devel] Re: fbcon slowness [was NTP on 2.4.2?] James Simmons
2001-04-02 22:44 ` Alan Cox
2001-04-03  6:23   ` Geert Uytterhoeven
2001-04-03 12:21     ` Alan Cox
2001-04-04  7:50       ` Eric W. Biederman [this message]
2001-04-04  8:47         ` Jamie Lokier
  -- strict thread matches above, loose matches on Subject: below --
2001-04-05  3:04 James Simmons
2001-04-05 12:03 ` Eric W. Biederman
2001-04-05 12:12   ` Geert Uytterhoeven
2001-04-05 13:15     ` Maciej W. Rozycki
2001-04-05 18:20       ` Eric W. Biederman
2001-04-06 10:09         ` Ivan Kokshaysky
2001-04-06 13:19           ` Eric W. Biederman
2001-04-06 17:27             ` Maciej W. Rozycki
2001-04-06 18:34               ` Andrea Arcangeli
2001-04-06 19:31                 ` Maciej W. Rozycki
2001-04-06 17:13           ` Maciej W. Rozycki
2001-04-08 18:11             ` Ivan Kokshaysky
2001-04-09 10:02               ` Maciej W. Rozycki
2001-04-09 11:05                 ` Ivan Kokshaysky
2001-04-06 17:07         ` Maciej W. Rozycki
2001-04-03  2:04 James Simmons
2001-04-01 14:54 James Simmons
2001-04-01 21:35 ` Jamie Lokier
2001-03-31  4:15 James Simmons
2001-03-31  3:47 James Simmons
2001-03-31 14:15 ` Jamie Lokier

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=m1lmphw1bi.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@linux-fbdev.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.