On Wed, Jan 30, 2008 at 09:40:43AM -0600, Serge E. Hallyn wrote:
> Quoting Dhaval Giani ([EMAIL PROTECTED]):
>
> Ok I figured resource mgmt and cgroups would be combined, but I'm fine
> splitting them. So can I do:
>
> cgroups: Paul Menage, Balbir
> Resource Management: dhaval, someone from open
Christoph Hellwig wrote:
> On Wed, Jan 30, 2008 at 02:41:34PM +0300, Denis V. Lunev wrote:
>> The pid of the locking daemon can be substituted with a task struct
>> without a problem. Namely, the value if filled in the context of the lockd
>> thread and used in lockd_up/lockd_down.
>>
>> It is poss
On Wed, Jan 30, 2008 at 02:41:34PM +0300, Denis V. Lunev wrote:
> The pid of the locking daemon can be substituted with a task struct
> without a problem. Namely, the value if filled in the context of the lockd
> thread and used in lockd_up/lockd_down.
>
> It is possible to save task struct instea
From: Pavel Emelyanov <[EMAIL PROTECTED]>
Date: Thu, 24 Jan 2008 16:15:13 +0300
> The comment about "race free view of the set of network
> namespaces" was a bit hasty. Look (there even can be only
> one CPU, as discovered by Alexey Dobriyan and Denis Lunev):
...
> Instead, I propose to crate t
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> From: Pierre Peiffer <[EMAIL PROTECTED]>
>
> In order to modify the semundo-list of a task from procfs, we must be able to
> work on any target task.
> But all the existing code playing with the semundo-list, currently works
> only on the 'current'
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> From: Pierre Peiffer <[EMAIL PROTECTED]>
>
> Today, the sem_undo_list is freed when the last task using it exits.
> There is no mechanism in place, that allows a safe concurrent access to
> the sem_undo_list of a target task and protects efficiently
Serge E. Hallyn wrote:
> Quoting Balbir Singh ([EMAIL PROTECTED]):
>> Cedric Le Goater wrote:
> == Topic ==
>
> Namespaces, containers, cgroups, and container checkpoint/restart.
>
> == Description ==
>
> Development for namespaces and cgroups is well underway in the
>>>
Quoting Balbir Singh ([EMAIL PROTECTED]):
> Cedric Le Goater wrote:
> >
> >>> == Topic ==
> >>>
> >>> Namespaces, containers, cgroups, and container checkpoint/restart.
> >>>
> >>> == Description ==
> >>>
> >>> Development for namespaces and cgroups is well underway in the
> >>> mainline kernel. T
Quoting Cedric Le Goater ([EMAIL PROTECTED]):
>
>> Why is that a conflict w.r.t resource management, isn't that more of a
>> cgroup
>> feature - task migration. We need task migration for resource management,
>> but
>> task migration is a system administrator/management function. I don't see
>>
Quoting Dhaval Giani ([EMAIL PROTECTED]):
> On Wed, Jan 30, 2008 at 02:28:13PM +0530, Balbir Singh wrote:
> > Kir Kolyshkin wrote:
> > > Serge E. Hallyn wrote:
> > >> Quoting Kir Kolyshkin ([EMAIL PROTECTED]):
> > >>
> > >>> Serge E. Hallyn wrote:
> > >>>
> > mini-summit:
> > I
Alexey Dobriyan wrote:
Propagate netns together with AF down to ->start/->next/->stop
iterators. Choose table based on netns and AF for showing.
Applied.
___
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
Alexey Dobriyan wrote:
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
include/linux/netfilter/x_tables.h |4 ++--
net/ipv4/netfilter/arp_tables.c| 21 ++---
net/ipv4/netfilter/ip_tables.c | 21 ++---
net/ipv6/netfilter/ip6_tables.c|
Alexey Dobriyan wrote:
Argh, there are many small but still wrong things with /proc/net/*_tables_*
so I decided to do overhaul simultaneously making it more suitable for
per-netns /proc/net/*_tables_* implementation.
Fix
a) xt_get_idx() duplicating now standard seq_list_start/seq_list_next
it
Why is that a conflict w.r.t resource management, isn't that more of a cgroup
feature - task migration. We need task migration for resource management, but
task migration is a system administrator/management function. I don't see the
conflict, but may be I am missing something very obvious.
Th
The pid of the locking daemon can be substituted with a task struct
without a problem. Namely, the value if filled in the context of the lockd
thread and used in lockd_up/lockd_down.
It is possible to save task struct instead and use it to kill the process.
The safety of this operation is guarante
On Wed, Jan 30, 2008 at 02:28:13PM +0530, Balbir Singh wrote:
> Kir Kolyshkin wrote:
> > Serge E. Hallyn wrote:
> >> Quoting Kir Kolyshkin ([EMAIL PROTECTED]):
> >>
> >>> Serge E. Hallyn wrote:
> >>>
> mini-summit:
> I will submit for a 1-day mini-summit. Some interesting
> >>>
Cedric Le Goater wrote:
>
>>> == Topic ==
>>>
>>> Namespaces, containers, cgroups, and container checkpoint/restart.
>>>
>>> == Description ==
>>>
>>> Development for namespaces and cgroups is well underway in the
>>> mainline kernel. To keep momentum going and keep the loosely
>>> knit teams of d
== Topic ==
Namespaces, containers, cgroups, and container checkpoint/restart.
== Description ==
Development for namespaces and cgroups is well underway in the
mainline kernel. To keep momentum going and keep the loosely
knit teams of developers well-coordinated, a physical meeting in
which t
Alexey Dobriyan wrote:
> On Tue, Jan 29, 2008 at 05:02:38PM +0100, [EMAIL PROTECTED] wrote:
>> This patch provides three new API to change the ID of an existing
>> System V IPCs.
>>
>> These APIs are:
>> long msg_chid(struct ipc_namespace *ns, int id, int newid);
>> long sem_chid(struct
Kir Kolyshkin wrote:
> Serge E. Hallyn wrote:
>> Quoting Kir Kolyshkin ([EMAIL PROTECTED]):
>>
>>> Serge E. Hallyn wrote:
>>>
mini-summit:
I will submit for a 1-day mini-summit. Some interesting
remaining topics for the mini-summit would include device
namespa
Serge E. Hallyn wrote:
Quoting Kir Kolyshkin ([EMAIL PROTECTED]):
Serge E. Hallyn wrote:
mini-summit:
I will submit for a 1-day mini-summit. Some interesting
remaining topics for the mini-summit would include device
namespaces, ttys and syslog, and lots of check
21 matches
Mail list logo
