Re: Jailed sysvipc implementation.

From: Pawel Jakub Dawidek (nick_at_garage.freebsd.pl)
Date: 06/25/03

  • Next message: Dmitry Sivachenko: "Re: Jailed sysvipc implementation." 
    Date: Wed, 25 Jun 2003 17:02:21 +0200
To: Dmitry Sivachenko <demon@freebsd.org>

    On Wed, Jun 25, 2003 at 06:52:33PM +0400, Dmitry Sivachenko wrote:
    +> > But you got still *one* memory zones for every jail and main host.
    +>
    +> Yes, that is exactly what I want.
    +> This is similar to separate IP stack for each jail: this is more powerful
    +> solution, but more expensive (uses more kernel memory).

    But note that my implementation allocates memory "on demand".
    If IPC syscall will not be used inside of jail memory will not be allocated.
    If think also that this will be trivial to add value to jail struct
    that will thell if we want separate IPC memory zones for this jail or not.

    +> Jail is not a true virtual machine.
    +> Let's keep it a *light* virtual machine replacement, with single IP stack,
    +> one memory zones for all jails and host, etc.

    I think it should be and it isn't now because of implementaion problems.
    Am I wrong? Poul? Robert? 

    -- 
Pawel Jakub Dawidek                       pawel@dawidek.net
UNIX Systems Programmer/Administrator     http://garage.freebsd.pl
Am I Evil? Yes, I Am!                     http://cerber.sourceforge.net

  • Next message: Dmitry Sivachenko: "Re: Jailed sysvipc implementation."

    Relevant Pages