From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: Jim Gettys <jg@pa.dec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: #define HZ 1024 -- negative effects?
Date: 29 Apr 2001 17:59:16 -0400 [thread overview]
Message-ID: <988581556.7879.2.camel@gromit> (raw)
In-Reply-To: <200104292144.f3TLiBD03874@pachyderm.pa.dec.com>
In-Reply-To: <200104292144.f3TLiBD03874@pachyderm.pa.dec.com>
Great. I'm running 4.02. How do I enable "silken mouse"?
Thanks,
-Michael
On 29 Apr 2001 14:44:11 -0700, Jim Gettys wrote:
> The biggest single issue in GUI responsiveness on Linux has been caused
> by XFree86's implementation of mouse tracking in user space.
>
> On typical UNIX systems, the mouse was often controlled in the kernel
> driver. Until recently (XFree86 4.0 days), the XFree86 server's reads
> of mouse/keyboard events were not signal driven, so that if the X server
> was loaded, the cursor stopped moving.
>
> On most (but not all) current XFree86 implementations, this is now
> signal drive, and further the internal X schedular has been reworked to
> make it difficult for a single client to monopolize the X server.
>
> So the first thing you should try is to make sure you are using an X server
> with this "silken mouse" enabled; anotherwords, run XFree86 4.0x and make
> sure the implementation has it enabled....
>
> There may be more to do in Linux thereafter, but until you've done this, you
> don't get to discuss the matter further....
> - Jim Gettys
>
> --
> Jim Gettys
> Technology and Corporate Development
> Compaq Computer Corporation
> jg@pa.dec.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-04-29 21:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 23:20 #define HZ 1024 -- negative effects? Michael Rothwell
2001-04-25 22:40 ` Nigel Gamble
2001-04-25 22:56 ` #define HZ 1024 -- negative effects Mark Hahn
2001-04-26 0:39 ` Michael Rothwell
2001-04-29 21:44 ` #define HZ 1024 -- negative effects? Jim Gettys
2001-04-29 21:59 ` Michael Rothwell [this message]
[not found] <fa.gh4u8sv.17i1q6@ifi.uio.no>
2001-04-26 2:02 ` Dan Maas
2001-04-26 2:30 ` Werner Puschitz
2001-04-26 3:51 ` Mike Galbraith
2001-04-28 8:23 ` Guus Sliepen
-- strict thread matches above, loose matches on Subject: below --
2001-04-26 18:19 Adam J. Richter
2001-04-26 18:31 ` Rik van Riel
2001-04-26 20:24 ` Dan Mann
2001-04-27 10:04 ` Mike Galbraith
2001-04-27 15:06 ` Dan Mann
2001-04-27 19:26 ` Nigel Gamble
2001-04-27 20:28 ` Mike Galbraith
2001-04-27 23:22 ` Nigel Gamble
2001-04-28 4:57 ` Mike Galbraith
2001-04-29 8:46 ` george anzinger
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=988581556.7879.2.camel@gromit \
--to=rothwell@holly-springs.nc.us \
--cc=jg@pa.dec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox