From: James Simmons <jsimmons@edgeglobal.com>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-mm@kvack.org, ggi-develop <ggi-develop@eskimo.com>,
FrameBuffer List <linux-fbdev@vuser.vu.union.edu>
Subject: Re: accel handling
Date: Mon, 30 Aug 1999 15:18:40 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.10.9908301507530.5887-100000@imperial.edgeglobal.com> (raw)
In-Reply-To: <m1aer9je4i.fsf@alogconduit1ae.ccr.net>
> C) We could simply put all processes that have the frame buffer
> mapped to sleep during the interval that the accel enginge runs.
That it!!!! You gave me a idea. I just realize I have been thinking about
it all wrong. Its not looking at if the framebuffer is being accessed but
to keep track of all the processes that have mmap the framebuffer device.
When the accel engine is ready to go we put all the processes that have
/dev/fb mmapped to sleep no matter if its being access or not. One thing
that I would have to make sure that the same process thats being put to
sleep isn't also the one trying to use the accel engine.
> F) It might be work bouncing this off of the ggi guys to see if they have
> satisfactorily solved this problem. Last I looked the ggi list was linux-ggi@eskimo.com
I'm one of those guys as well as a kernel developer.
--
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-30 19:18 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
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 [this message]
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=Pine.LNX.4.10.9908301507530.5887-100000@imperial.edgeglobal.com \
--to=jsimmons@edgeglobal.com \
--cc=ebiederm+eric@ccr.net \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=ggi-develop@eskimo.com \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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