linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: Vladimir Dergachev <vdergach@sas.upenn.edu>,
	linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: accel handling
Date: Tue, 31 Aug 1999 13:49:23 +0100 (BST)	[thread overview]
Message-ID: <14283.53075.795656.291744@dukat.scot.redhat.com> (raw)
In-Reply-To: <37CBB49E.C52C5D99@switchboard.ericsson.se>

Hi,

On Tue, 31 Aug 1999 12:55:26 +0200, Marcus Sundberg
<erammsu@kieraypc01.p.y.ki.era.ericsson.se> said:

> But by only re-mapping the framebuffer on demand as Stephen said you
> can avoid repeatedly un-mapping the framebuffer for processes/threads
> that doesn't use it.

Yes.  The biggest problem is that the VM currently has no support for
demand-paging of an entire framebuffer region, and taking a separate
page fault to fault back the mapping of every page in the framebuffer
would be too slow.  As long as we can switch the entire framebuffer in
and out of the mapping rapidly, things aren't too bad.

Even on an SMP box with threads, the overhead is probably acceptable if
we are switching at no more than frame rate.  However, for low latency,
high throughput graphics, I'm guessing we'd be driving the accel engine
a lot faster than that, and we also have the problem that many graphics
operations will require fine interleaving of (and hence fast switching
between) accelerated and framebuffer access.  VM enforcement simply is
not fast enough for this.

--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/

  reply	other threads:[~1999-08-31 12:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
1999-08-29 14:57 James Simmons
1999-08-31  3:39 Jens Owen
1999-08-31 12:51 ` 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.53075.795656.291744@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linux-mm@kvack.org \
    --cc=vdergach@sas.upenn.edu \
    /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