> I suppose as a cleaner alternative we could
> add a container_subsys->inherit_defaults() handler, to be called at
> container_clone(), and for cpusets this would set cpus and mems to
> the parent values - sibling exclusive values. If that comes to nothing,
> then the attach_task() is still refu
Quoting Paul Jackson ([EMAIL PROTECTED]):
> > > I wasn't paying close enough attention to understand why you couldn't
> > > do it in two steps - make the container, and then populate it with
> > > resources.
> >
> > Sorry, please clarify - are you saying that now you do understand, or
> > that I s
> > I wasn't paying close enough attention to understand why you couldn't
> > do it in two steps - make the container, and then populate it with
> > resources.
>
> Sorry, please clarify - are you saying that now you do understand, or
> that I should explain?
Could you explain -- I still don't und
Quoting Paul Jackson ([EMAIL PROTECTED]):
> > Would it then make sense to just
> > default to (parent_set - sibling_exclusive_set) for a new sibling's
> > value?
>
> Which could well be empty, which in turn puts one back in the position
> of dealing with a newborn cpuset that is empty (of cpus or
From: Daniel Lezcano <[EMAIL PROTECTED]>
Date: Wed, 06 Jun 2007 22:38:11 +0200
> Perhaps, a name like "epipe" or "npipe", which reflects what does the
> device, is more appropriate ?
'npipe' (Network PIPE) or 'epipe' (Ethernet PIPE) are fine with me.
_
David Miller wrote:
From: Pavel Emelianov <[EMAIL PROTECTED]>
Date: Wed, 06 Jun 2007 19:11:38 +0400
Veth stands for Virtual ETHernet. It is a simple tunnel driver
that works at the link layer and looks like a pair of ethernet
devices interconnected with each other.
I would suggest cho
From: Pavel Emelianov <[EMAIL PROTECTED]>
Date: Wed, 06 Jun 2007 19:11:38 +0400
> Veth stands for Virtual ETHernet. It is a simple tunnel driver
> that works at the link layer and looks like a pair of ethernet
> devices interconnected with each other.
I would suggest choosing a different name.
'
On Wed, 06 Jun 2007 19:11:38 +0400
Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> Veth stands for Virtual ETHernet. It is a simple tunnel driver
> that works at the link layer and looks like a pair of ethernet
> devices interconnected with each other.
>
> Mainly it allows to communicate between net
Pavel Emelianov wrote:
> +MODULE_DESCRIPTION("Virtual Ethernet Tunnel");
> +MODULE_LICENSE("GPL v2");
This seems to be missing MODULE_ALIAS_RTNL_LINK("veth");
___
Containers mailing list
[EMAIL PROTECTED]
https://lists.linux-foundation.org/mailman/listi
Pavel Emelianov wrote:
> Veth stands for Virtual ETHernet. It is a simple tunnel driver
> that works at the link layer and looks like a pair of ethernet
> devices interconnected with each other.
>
> Mainly it allows to communicate between network namespaces but
> it can be used as is as well.
>
>
On Wed, 2007-06-06 at 13:37 +0200, Mark Pflueger wrote:
> hi everyone!
>
> i'm not subscribed to the list, so if you care to flame because of my noob
> question, just do it to the list, otherwise please cc me.
>
> i'm trying to write a checkpoint/restore module for processes and so have
> a bas
Serge E. Hallyn wrote:
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
The socket relies on the sockfs. In some cases, the socket are orphans and
it is not possible to access them via a file descriptor, this is the case for
example for timewait sockets. Hopefully, an inode is still usable to s
Pavel Emelianov wrote:
> diff --git a/ip/iplink.c b/ip/iplink.c
> index 5170419..6975990 100644
> --- a/ip/iplink.c
> +++ b/ip/iplink.c
> @@ -287,7 +287,7 @@ static int iplink_modify(int cmd, unsign
>strlen(type));
>
> lu = get_link_type(type);
> -
The usage is
# ip link add [name] type veth [peer ] [mac ] [peer_mac ]
The Makefile is maybe not as beautiful as it could be. It
is to be discussed.
One thing I noticed during testing is the following. When launching
this with link_veth.so module and not specifying any module specific
parameters,
Veth stands for Virtual ETHernet. It is a simple tunnel driver
that works at the link layer and looks like a pair of ethernet
devices interconnected with each other.
Mainly it allows to communicate between network namespaces but
it can be used as is as well.
Eric recently sent a similar driver ca
Quoting Cedric Le Goater ([EMAIL PROTECTED]):
> Mark Pflueger wrote:
> > hi everyone!
> >
> > i'm not subscribed to the list, so if you care to flame because of my noob
> > question, just do it to the list, otherwise please cc me.
>
> you should subscribe to [EMAIL PROTECTED] and send your ideas
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> The socket relies on the sockfs. In some cases, the socket are orphans and
> it is not possible to access them via a file descriptor, this is the case for
> example for timewait sockets. Hopefully, an inode is still usable to specify
> a socket. This
Cedric Le Goater wrote:
Serge E. Hallyn wrote:
Last year we all met for breakfast at OLS. Now we've all pretty much
all already met so maybe it's less exciting, but do people (who will be
at OLS) care to meet for breakfast on the thursday or friday?
OK for me, if i can skip the pancak
Serge E. Hallyn wrote:
> Last year we all met for breakfast at OLS. Now we've all pretty much
> all already met so maybe it's less exciting, but do people (who will be
> at OLS) care to meet for breakfast on the thursday or friday?
OK for me, if i can skip the pancakes with tons of cream and jam.
Mark Pflueger wrote:
> hi everyone!
>
> i'm not subscribed to the list, so if you care to flame because of my noob
> question, just do it to the list, otherwise please cc me.
you should subscribe to [EMAIL PROTECTED] and send your ideas on that
list. There's a BOF on that topic at OLS if you can
From: Daniel Lezcano <[EMAIL PROTECTED]>
This patch defines a set of netlink attributes to store/retrieve udp
option and endpoints. The logic is to extend the netlink message attribute
to take into account these new values.
The ops of struct sock is extended with the dump/restore callbacks, so wh
From: Daniel Lezcano <[EMAIL PROTECTED]>
This patch defines a set of netlink attributes to store/retrieve inet
options. The logic is to extend the netlink message attribute to take into
account these new values.
The multicast list is browsed first and the netlink nested attribute is filled
in t
From: Daniel Lezcano <[EMAIL PROTECTED]>
This patch defines a set of netlink attributes to store/retrieve socket
options.
* At dump time, a netlink message specify the inode of the socket to
be checkpointed. The socket is retrieved with the inode number. A
new netlink message is built in
From: Daniel Lezcano <[EMAIL PROTECTED]>
This patchset provide the AF_INET C/R option in the makefile and a generic
netlink framework for passing the socket messages.
It seems that we are encouraged to use netlink instead of the /proc, /sysfs,
ioctls:
http://kerneltrap.org/node/6637
I found th
The socket relies on the sockfs. In some cases, the socket are orphans and
it is not possible to access them via a file descriptor, this is the case for
example for timewait sockets. Hopefully, an inode is still usable to specify
a socket. This one can be retrieved from /proc/net/tcp for orphan soc
Hi,
I would like to resurect the discussion we had concerning the socket
checkpoint/restart.
I began to look how to checkpoint them. I thought the following:
The socket can be checkpointed one by one from userspace.
That will allow to provide a mechanism to application which wants to
checkpoi
Hi, Andrew/Paul,
Here's the latest version of containerstats ported to v10. Could you
please consider it for inclusion
Changelog
1. Instead of parsing long container path's use the dentry to match the
container for which stats are required. The user space application
opens the container di
My apologies, but I won't be able to visit OLS this year :/
I think Kirill Kolyshkin and Denis Lunev will be glad to meet you again!
Hope Pavel Emelianov will be able to join as well.
Thanks,
Kirill
Serge E. Hallyn wrote:
> Last year we all met for breakfast at OLS. Now we've all pretty much
>
Cedric Le Goater wrote:
>> The flat model has many optimization ways in comparison with the multilevel
>> one. Like we can cache the pid value on structs and some other.
>>
>> Moreover having generic level nesting sounds reasonable. Having single level
>> nesting - too as all the namespace we have
29 matches
Mail list logo
