From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jens Owen <jens@precisioninsight.com>
Cc: linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: accel handling
Date: Tue, 31 Aug 1999 13:51:55 +0100 (BST) [thread overview]
Message-ID: <14283.53227.275065.227789@dukat.scot.redhat.com> (raw)
In-Reply-To: <37CB4E69.8C441E27@precisioninsight.com>
Hi,
On Mon, 30 Aug 1999 21:39:21 -0600, Jens Owen
<jens@precisioninsight.com> said:
> Don't know if this would be any help to this discussion, be we have
> some writeups on the mechanisms we use for the DRI at
> http://www.precisioninsight.com/dr/ the most useful might be
> locking.html
Thanks. Yes, this is exactly what I've been saying all along --- if you
want to make things go fast enough, you need cooperative locking.
Physically enforcing it in the VM wil never be able to keep up with the
pace.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-08-31 12:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-31 3:39 Jens Owen
1999-08-31 12:51 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-08-29 14:57 James Simmons
1999-08-29 14:52 James Simmons
1999-08-29 16:14 ` Stephen C. Tweedie
1999-08-30 1:14 ` James Simmons
1999-08-30 10:44 ` Stephen C. Tweedie
1999-08-30 12:06 ` Marcus Sundberg
1999-08-30 14:18 ` Stephen C. Tweedie
1999-08-30 14:50 ` James Simmons
1999-08-30 15:52 ` Stephen C. Tweedie
1999-08-30 17:51 ` James Simmons
1999-08-30 20:27 ` Stephen C. Tweedie
1999-08-31 0:28 ` Vladimir Dergachev
1999-08-31 10:55 ` Marcus Sundberg
1999-08-31 12:49 ` Stephen C. Tweedie
1999-08-31 17:10 ` James Simmons
1999-08-31 18:44 ` Stephen C. Tweedie
1999-08-30 14:31 ` James Simmons
1999-08-30 18:51 ` Eric W. Biederman
1999-08-30 19:18 ` James Simmons
1999-08-30 21:39 ` Andreas Beck
1999-08-30 20:36 ` Stephen C. Tweedie
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=14283.53227.275065.227789@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=jens@precisioninsight.com \
--cc=linux-mm@kvack.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