OpenVZ Forum


Home » Mailing lists » Users » Docs to understand how OpenVZ is implemented.
Re: Docs to understand how OpenVZ is implemented. [message #47767 is a reply to message #47753] Fri, 07 September 2012 23:10 Go to previous message
Andrew Vagin is currently offline  Andrew Vagin
Messages: 28
Registered: November 2011
Junior Member
On Fri, Sep 07, 2012 at 05:17:28PM +0400, Kentaro Ebisawa wrote:
> Hi,
>
> Are there any documents/blogs/books I should read to understand how OpenVZ is implemented?
> I went over http://wiki.openvz.org/Main_Page , searched Google but could not find details.
>
> I'm especially interested in networking code.
> For example ...
> * What was added to networking code?
> vzethdev.c and what?
> * code path difference compared to vanilla kernel when receiving/sending packet.
> * How cgroup is used.

A new net namespace is create for each CT. Two types of network
devices can be used for connectivity with external networks:
http://wiki.openvz.org/Veth
http://wiki.openvz.org/Venet

UBC have a few limits for network buffers.
http://wiki.openvz.org/UBC_secondary_parameters

You can look at patch-042stab061 in
http://download.openvz.org/kernel/branches/rhel6-2.6.32-test ing/042stab061.8/vzkernel-2.6.32-042stab061.8.src.rpm
This patch contains only OpenVZ changes.

>
> I'm trying to read the source code but wanted to know overall design for better and faster understanding.
> Please let me know if this is better question for devel@openvz.org.
>
> Thanks!
> --
> Kentaro Ebisawa <ebiken.g@gmail.com>
>

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: Looking for Gentoo ebuild for sys-kernel/openvz-sources-2.6.32.57.1
Next Topic: how can i easily replicate a container?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Apr 18 22:54:24 GMT 2026

Total time taken to generate the page: 0.42835 seconds
Powered by FUDforum Powered by Virtuozzo Containers