All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4 kernel problem
Date: Tue, 10 Apr 2001 22:30:41 -0700	[thread overview]
Message-ID: <200104110530.WAA00945@dave.xdr.com> (raw)

XFree86 X window updates are slower on 2.4 than 2.2, by a significant amount.
I've observed this comparing 2.2.18 with 2.4.1 and one of the 2.4.pre kernels.
I've seen it with ATI Rage 128, Geforce 1 and GeForce 2 MX. I've seen it on
two different computers, both Athlon based. Just any rectangular copies to
an X window are slow on 2.4 and much faster under 2.2.18.

I'm using DRI and accelerated GLX servers so I get good 3d, but 2d is
suffering in a *big* way. Here are some frames/second for a simple program:


Using shared memory       Kernel       frames/second
     yes                   2.4              39
     no                    2.4              30
     yes                   2.2.18          245
     no                    2.2.18           88

I can't get any response from the XFree86 team. I know I'm not the only
one with this trouble, something has been broken in the 2.4.

Thanks--
Dave
dash@xdr.com

             reply	other threads:[~2001-04-11  5:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11  5:30 David Ashley [this message]
2001-04-11 12:41 ` 2.4 kernel problem Alan Cox

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=200104110530.WAA00945@dave.xdr.com \
    --to=dash@xdr.com \
    --cc=linux-kernel@vger.kernel.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 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.