From: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
To: Vladimir Dergachev <vdergach@sas.upenn.edu>
Cc: linux-mm@kvack.org
Subject: Re: accel handling
Date: Tue, 31 Aug 1999 12:55:26 +0200 [thread overview]
Message-ID: <37CBB49E.C52C5D99@switchboard.ericsson.se> (raw)
In-Reply-To: <Pine.GSO.4.10.9908302023470.15357-100000@mail1.sas.upenn.edu>
Vladimir Dergachev wrote:
>
> On Mon, 30 Aug 1999, Stephen C. Tweedie wrote:
>
> > Hi,
> > The only way to do it is to flip page tables while the accel engine is
> > running. You may want to restore it on demand by trapping the page
> > fault on the framebuffer and stalling until the accel lock is released.
> > This can be done, but it is really expensive: you are doing a whole pile
> > of messy VM operations every time you want to trigger the accel engine
> > (any idea how often you want to flip the protection, btw?)
[snip]
> What about forbidding concurrency for the processes that have mmapped
> the framebuffer/accelerator ? Say assign all of them to one(or same) cpu
> permanently.
Not an acceptable solution. You may have several threads clone()d off
after the framebuffer have been mapped, and they may not do anything
related to graphics.
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.
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan/
Royal Institute of Technology | Phone: +46 707 295404
Stockholm, Sweden | E-Mail: mackan@stacken.kth.se
--
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 10:55 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 [this message]
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
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=37CBB49E.C52C5D99@switchboard.ericsson.se \
--to=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