Re: How much of a mess does OpenVZ make? ;) Was: What can OpenVZ do?
flat view
From: Alexey Dobriyan <hidden>
Date: 2009-02-26 15:51:30
Also in:
linux-mm, lkml
On Thu, Feb 12, 2009 at 03:04:05PM -0800, Dave Hansen wrote:
dave@nimitz:~/kernels/linux-2.6-openvz$ git diff v2.6.27.10... kernel/cpt/ | diffstat Makefile | 53 + cpt_conntrack.c | 365 ++++++++++++ cpt_context.c | 257 ++++++++ cpt_context.h | 215 +++++++ cpt_dump.c | 1250 ++++++++++++++++++++++++++++++++++++++++++ cpt_dump.h | 16 cpt_epoll.c | 113 +++ cpt_exports.c | 13 cpt_files.c | 1626 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ cpt_files.h | 71 ++ cpt_fsmagic.h | 16 cpt_inotify.c | 144 ++++ cpt_kernel.c | 177 ++++++ cpt_kernel.h | 99 +++ cpt_mm.c | 923 +++++++++++++++++++++++++++++++ cpt_mm.h | 35 + cpt_net.c | 614 ++++++++++++++++++++ cpt_net.h | 7 cpt_obj.c | 162 +++++ cpt_obj.h | 62 ++ cpt_proc.c | 595 ++++++++++++++++++++ cpt_process.c | 1369 ++++++++++++++++++++++++++++++++++++++++++++++ cpt_process.h | 13 cpt_socket.c | 790 ++++++++++++++++++++++++++ cpt_socket.h | 33 + cpt_socket_in.c | 450 +++++++++++++++ cpt_syscalls.h | 101 +++ cpt_sysvipc.c | 403 +++++++++++++ cpt_tty.c | 215 +++++++ cpt_ubc.c | 132 ++++ cpt_ubc.h | 23 cpt_x8664.S | 67 ++ rst_conntrack.c | 283 +++++++++ rst_context.c | 323 ++++++++++ rst_epoll.c | 169 +++++ rst_files.c | 1648 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ rst_inotify.c | 196 ++++++ rst_mm.c | 1151 +++++++++++++++++++++++++++++++++++++++ rst_net.c | 741 +++++++++++++++++++++++++ rst_proc.c | 580 +++++++++++++++++++ rst_process.c | 1640 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ rst_socket.c | 918 +++++++++++++++++++++++++++++++ rst_socket_in.c | 489 ++++++++++++++++ rst_sysvipc.c | 633 +++++++++++++++++++++ rst_tty.c | 384 +++++++++++++ rst_ubc.c | 131 ++++ rst_undump.c | 1007 ++++++++++++++++++++++++++++++++++ 47 files changed, 20702 insertions(+) One important thing that leaves out is the interaction that this code has with the rest of the kernel. That's critically important when considering long-term maintenance, and I'd be curious how the OpenVZ folks view it.
OpenVZ as-is in some cases wants some functions to be made global (and if C/R code will be modular, exported). Or probably several iterators added. But it's negligible amount of changes compared to main code. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html