Re: RFC [patch 13/34] PID Virtualization Define new task_pid api

How can you migrate application which consists of two processes doing IPC via signals? They are not tired inside kernel anyhow and there is

no way to automatically detect that both should be migrated together.

VPSs what provides you such kind of boundaries of what should be considered as a whole.

Could you explain a little bit _how_ VPSs provide this?

OpenVZ virtualizes kernel resources such as IPC making them per-VPS. Processes in VPS deal with such virtualized resources, so they efficiently should be migrated together. That's it - a whole container with its resources should be considered as a whole.

Signals are not virtualized in this manner since they are rather per-task resource, but OpenVZ introduces strict boundaries in kernel which make sure that no any 3rd task from another container (VPS) will be participating in the communication.

Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • RFC [patch 00/34] PID Virtualization Overview
    • From: Serge Hallyn <[email protected]>
  • RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Serge Hallyn <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Arjan van de Ven <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: "Serge E. Hallyn" <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Alan Cox <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Dave Hansen <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Greg KH <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Dave Hansen <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: [email protected] (Eric W. Biederman)
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Hubertus Franke <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Linus Torvalds <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Kirill Korotaev <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: [email protected] (Eric W. Biederman)
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Kirill Korotaev <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: [email protected] (Eric W. Biederman)
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Kirill Korotaev <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: [email protected] (Eric W. Biederman)
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Kirill Korotaev <[email protected]>
  • Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
    • From: Dave Hansen <[email protected]>

• Prev by Date: Re: [ 00/10] [Suspend2] Modules support.
• Next by Date: Re: FYI: RAID5 unusably unstable through 2.6.14
• Previous by thread: Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
• Next by thread: Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]