Roadmap for features planed for containers where and Some future features ideas.

Peter Dolding oiaohm at
Sat Jul 26 22:17:39 PDT 2008

On Sat, Jul 26, 2008 at 11:56 PM, Eric W. Biederman
<ebiederm at> wrote:
> "Peter Dolding" <oiaohm at> writes:
>> Issue is light-weight proxy fails as soon as you start dealing with
>> the GPU processing stuff.
>> This has already been fairly heavily researched.   Complete system
>> suspend works because you take the complete gpu off line and restore
>> it back to where it was on the same GPU.
> Darn.  2D X (the last I looked at it) has the property where the applications
> are required at any point to be able to repaint all of their windows.  It sounds
> like this is not the case for 3D X applications and it is a real shame.
> I also suspect that even if I use the repaint trick do it in such a way
> that I am allowed to switch the gpu buggy applications will fail.

All opengl and gpu using programs would fail to that switch.   Reason
3d data was sent to video card for processing into a texture then
display for non gpu opengl.   If you have those calls captured and
recorded you can replay them.  With non gpu opengl it is possible to
keep a active list of data to put back as long as they don't use any
vendor dependant extensions.  Same model card would work here even
with extentions.

3d program moves far more data than 2d and could not afford to be
sending it all the time.

>> Migration is worse than you can dream.  Even the same model GPU loaded
>> with a different GPU save state can fail if maker has altered paths
>> due to damage in 1 chip.  I see no trick around this.  Even GPU's on
>> the same card can fail if you try to restore the wrong state back into
>> them.
> Not really.  I know that direct hardware access by application programs
> is a problem.   My practical question is how robust programs are to hardware
> hotplug.

Most opengl programs are not robust to hotplug of video card so answer
that with crash if there active card is removed and don't detect and
use the added opengl card until they get to a detection point.

>> Using a light-weight proxy you will be able to tag applications using
>> advanced GPU instructions that will not migrate or suspend happily.
> That sounds very practical.
>>  Is one of the ones you will want to work
>> with when building a light weight proxy.   This allows X11
>> applications to be disconnected from one X11 server and connected to
>> another.
>> Also got so far along
>> forwarding opengl.
>> Its more you will have to sort.  It will break down into 4.
>> 2d and maybe some opengl suspendable because interface can be simplely
>> regenerated on a new X11 server using nothing GPU targeted.
>> Using GPU heavily with a detectable resend of everything to gpu with
>> corrections for change of video card.   This would cover some games
>> that at change of level and restart game engine with diagnostics.
>> This would be more setting fixed suspend points where application
>> could only be suspended at those points.  Some applications that do
>> some gpu off loading of tasks.   Ie comes like trying to stop a
>> critical section of kernel have to wait.
>> Using GPU no clean suspend points.   Has to be lost in the suspend or
>> transfer process.
> Yep.
>> GPU is the problem.   Most of the other rendering stuff is simple to
>> solve.   GPU are a stack of rogue threads.
>> There is no magical way around this problem.   We all wish there were.
>>   Every nice virtual solution is a brick wall.  Mixed solution is
>> kinda needed.   Also the reason why I did not care if desktop use
>> complete broke mean to migrate and suspend its a lot simpler that way.
> Totally and if we have the capabilities today to make it work without
> the possibility of suspend/resume I am happy with that.
>> Of course you might dream up some way I have not even considered.
> Certainly worth thinking about.
> For I am concerned with getting the basics working solid.  So I don't
> plan on working on any of this any time soon.  Other contributions
> are welcome.
>> Peter Dolding
>> PS own GPU language will only work for newly code applications also
>> will be slower as some programs build there own gpu code locallly in
>> advance and upload it on demand.
> Nah.  I'm happy so long as we have a way to say: "Hey!  You silly application
> that was talking directly to the hardware.  You have to deal with new hardware
> now.  Cope."
> Eric
I think having a two messages.   Hey program I am going to nick your
hardware prepare yourself before suspend and then you possible have
new hardware cope.  This could become like a general way for all
direct hardware using programs.

Peter Dolding

More information about the Containers mailing list