Hi Serge,
I can confirm the room and we can get you some type of a paper/white
board. I should know tomorrow about the speakerphone and Internet
access.
C.
Hi C.,
I'm sorry after all the emails I'm not straight on what we're actually
getting. We have a U-shaped room, but do we have a
On Wed, Jul 09, 2008 at 10:57:10AM -0500, Serge E. Hallyn wrote:
Before I forget,
we're planning on having a call-in for the containers mini-summit. The
phone number is:
US toll: 1-770-615-1382
US toll-free: 1-877-421-0023
When asked, the passcode is: 499229
I was
2008/7/25 Balbir Singh [EMAIL PROTECTED]:
There are applications that can/need to handle overcommit, just that we are
not
aware of them fully. Immediately after our meeting, I was pointed to
Hello Oren,
That is great, that you have proposed your version of checkpointing/restart.
In a few days I will send a patchset with OpenVZ checkpointing/restart.
So, we will be able to compare our approaches and take the best parts from
both.
Regards,
Andrey
On Wednesday 30 July 2008 07:24 Oren
Oren Laadan wrote:
Disclaimer: long reply :)
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
In the recent mini-summit at OLS 2008 and the following days it was
agreed to tackle the checkpoint/restart (CR) by beginning with a very
simple case: save and restore a single
Quoting Louis Rilling ([EMAIL PROTECTED]):
On Wed, Jul 30, 2008 at 10:40:35AM -0700, Dave Hansen wrote:
On Wed, 2008-07-30 at 11:52 -0500, Serge E. Hallyn wrote:
This list is getting on my nerves. Louis, I'm sorry the threading
is going to get messed up.
I think I just cleared
Louis Rilling wrote:
On Wed, Jul 30, 2008 at 02:27:52PM -0400, Oren Laadan wrote:
Louis Rilling wrote:
+/**
+ * cr_vma_fill_pgarr - fill a page-array with addr/page tuples for a vma
+ * @ctx - checkpoint context
+ * @pgarr - page-array to fill
+ * @vma - vma to scan
+ * @start - start
Daniel Lezcano wrote:
Oren Laadan wrote:
Disclaimer: long reply :)
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
In the recent mini-summit at OLS 2008 and the following days it was
agreed to tackle the checkpoint/restart (CR) by beginning with a very
simple case: save
Louis Rilling wrote:
On Thu, Jul 31, 2008 at 11:09:54AM -0400, Oren Laadan wrote:
Louis Rilling wrote:
On Wed, Jul 30, 2008 at 06:20:32PM -0400, Oren Laadan wrote:
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
+int do_checkpoint(struct cr_ctx *ctx)
+{
+int ret;
Oren Laadan wrote:
Daniel Lezcano wrote:
Oren Laadan wrote:
Disclaimer: long reply :)
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
In the recent mini-summit at OLS 2008 and the following days it was
agreed to tackle the checkpoint/restart (CR) by beginning with a very
Hi Pavel,
Here is the 'hijack' patch that was mentioned during the namespaces
part of the containers mini-summit. It's a proposed way of entering
namespaces.
It's been rotting for awhile as you can see by the changelog, but
hopefully I updated it sufficiently and correctly.
-serge
From
Louis Rilling wrote:
On Thu, Jul 31, 2008 at 12:28:57PM -0400, Oren Laadan wrote:
Louis Rilling wrote:
On Thu, Jul 31, 2008 at 11:09:54AM -0400, Oren Laadan wrote:
Louis Rilling wrote:
On Wed, Jul 30, 2008 at 06:20:32PM -0400, Oren Laadan wrote:
Serge E. Hallyn wrote:
Quoting Oren Laadan
Quoting Oren Laadan ([EMAIL PROTECTED]):
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
+int do_checkpoint(struct cr_ctx *ctx)
+{
+ int ret;
+
+ /* FIX: need to test whether container is checkpointable */
+
+ ret = cr_write_hdr(ctx);
+ if (!ret)
+
Quoting Andrey Mirkin ([EMAIL PROTECTED]):
Hello Oren,
That is great, that you have proposed your version of checkpointing/restart.
In a few days I will send a patchset with OpenVZ checkpointing/restart.
So, we will be able to compare our approaches and take the best parts from
both.
Hello list,
I hope this is the right place to post.
I've recently moved to 2.6.26 git (i hope that's the bleeding edge) OpenVZ
to find out how usable it is. I'm running it on a box under fair IO load
(100-300 BIO/s). The thing panics in net/ipv4/tcp_ipv4.c:tcp_v4_send_ack()
once every couple of
Hi, I'm going to send this once networking people will start accepting
new stuff.
Please, try and test on your favourite bridging setup, I'm currently
very limited in this.
To try ebtables, apply this patch first:
diff --git a/net/netfilter/core.c b/net/netfilter/core.c
index 292fa28..c4065b8
Allow creation of bridges in netns.
Bridge netdevice doesn't cross netns boundaries.
Additions and deletions are done with netdevices in the same netns.
Process notifications in netns, too.
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
net/bridge/br_device.c |3 ++-
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
net/bridge/br.c | 22 --
net/bridge/br_if.c |4 ++--
net/bridge/br_private.h |2 +-
3 files changed, 19 insertions(+), 9 deletions(-)
--- a/net/bridge/br.c
+++ b/net/bridge/br.c
@@ -28,6 +28,10 @@
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
include/net/net_namespace.h |4
include/net/netns/bridge.h |9 +
net/bridge/netfilter/ebtables.c |8
3 files changed, 17 insertions(+), 4 deletions(-)
--- a/include/net/net_namespace.h
+++
Register ebtable in netns.
For this duplicate table at the very beginning. This is done so we won't
add one table first to table list of netns#1, then overwrite list_head
when adding to table list of netns #2, and so on.
P.S.: Addition of underscored variables is temporary and will go away in
a
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
include/net/netns/bridge.h|1
net/bridge/netfilter/ebtable_broute.c | 35 ++
2 files changed, 28 insertions(+), 8 deletions(-)
--- a/include/net/netns/bridge.h
+++
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
include/net/netns/bridge.h |1
net/bridge/netfilter/ebtable_nat.c | 47 +
2 files changed, 33 insertions(+), 15 deletions(-)
--- a/include/net/netns/bridge.h
+++ b/include/net/netns/bridge.h
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
include/net/netns/bridge.h|1
net/bridge/netfilter/ebtable_filter.c | 50 +-
2 files changed, 38 insertions(+), 13 deletions(-)
--- a/include/net/netns/bridge.h
+++
Bridge netfilter code uses fake netdevice and fake rtable. Fake means
static struct net_device. So these should be logically created in
bridge's portion of struct netns.
But!
Adding struct net_device __fake_net_device creates header circular dependency,
which is PITA to resolve. I couldn't, so
So far table could be unregistered only during module unload.
Which didn't happen, because depending on table entries, module was
pinned enough times to prevent unload at all.
Now table will be unregistered during netns stop, so prevent module
refcount leaks by cleaning up table entries at table
This patch series introduces a cgroup subsystem that utilizes the swsusp
freezer to freeze a group of tasks. It's immediately useful for batch job
management scripts. It should also be useful in the future for implementing
container checkpoint/restart.
The freezer subsystem in the container
Don't let frozen tasks or cgroups change. This means frozen tasks can't
leave their current cgroup for another cgroup. It also means that tasks
cannot be added to or removed from a cgroup in the FROZEN state. We
enforce these rules by checking for frozen tasks and cgroups in the
can_attach()
This patch implements a new freezer subsystem in the control groups framework.
It provides a way to stop and resume execution of all tasks in a cgroup by
writing in the cgroup filesystem.
The freezer subsystem in the container filesystem defines a file named
freezer.state. Writing FROZEN to the
Use the new cgroup write_string method rather than the raw write method
because it better matches the needs of the freezer cgroup subsystem.
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
---
kernel/cgroup_freezer.c | 21 +
1 file changed, 5 insertions(+), 16 deletions(-)
Now that the TIF_FREEZE flag is available in all architectures,
extract the refrigerator() and freeze_task() from kernel/power/process.c
and make it available to all.
The refrigerator() can now be used in a control group subsystem
implementing a control group freezer.
Signed-off-by: Cedric Le
When a system is resumed after a suspend, it will also unfreeze
frozen cgroups.
This patchs modifies the resume sequence to skip the tasks which
are part of a frozen control group.
Signed-off-by: Cedric Le Goater [EMAIL PROTECTED]
Signed-off-by: Matt Helsley [EMAIL PROTECTED]
Acked-by: Serge E.
This patch is the first step in making the refrigerator() available
to all architectures, even for those without power management.
The purpose of such a change is to be able to use the refrigerator()
in a new control group subsystem which will implement a control group
freezer.
Signed-off-by:
On Thu, 2008-07-31 at 22:06 -0700, Matt Helsley wrote:
This patch series introduces a cgroup subsystem that utilizes the swsusp
freezer to freeze a group of tasks. It's immediately useful for batch job
management scripts. It should also be useful in the future for implementing
container
33 matches
Mail list logo
