Michael Kerrisk wrote:
> Hi Daniel,
>
> Please CC linux-api on API/ABI changes.
>
> See Documentation/SubmitChecklist and
> http://thread.gmane.org/gmane.linux.ltp/5658.
Will do, thanks.
-- Daniel
___
Containers mailing list
[EMAIL PROTECTED]
https
Ian jonhson wrote:
> Thank Daniel, Serge, and all the friends in the maillist.
> Now, I have given a bird view about current status of container.
> The finial question is that how to do contribution:
> * what matters/fashion should I obey to develop codes?
> * how to upload my patch or my extension
Daniel Lezcano wrote:
> This patchset (not tested) shows how it is possible to create a socket
> specifying the network namespace destination. That should allow a single
> process to handle several network namespaces.
Vivien, Andreas,
does this patch fit your needs ? If so, I ca
Serge E. Hallyn wrote:
> Quoting Daniel Lezcano ([EMAIL PROTECTED]):
>> Daniel Hokka Zakrisson wrote:
>>> Daniel Lezcano wrote:
>>>
>>> Wouldn't it be better to simply remove CAP_SYS_BOOT from containers
>>> until sys_reboot emits some signal to
Serge E. Hallyn wrote:
> Quoting Daniel Lezcano ([EMAIL PROTECTED]):
>> Daniel Hokka Zakrisson wrote:
>>> Daniel Lezcano wrote:
>>>
>>> Wouldn't it be better to simply remove CAP_SYS_BOOT from containers
>>> until sys_reboot emits some signal to
Ian jonhson wrote:
> Dear all,
>
> I am now working in the development of user tool for container
> (built by Daniel Lezcano) and interest in the accounting
> of container. Now, I would like to know whether the patches stated
> in:
> http://lwn.net/Articles/229974/
I think
Daniel Hokka Zakrisson wrote:
> Daniel Lezcano wrote:
>
> Wouldn't it be better to simply remove CAP_SYS_BOOT from containers
> until sys_reboot emits some signal to userspace to restart/halt the
> container? (This is what we do in Linux-VServer.)
Ok, I will try, thanks.
Subject: disable sys_reboot when not in init_pid_ns
From: Daniel Lezcano <[EMAIL PROTECTED]>
This simple patch avoid to shutdown the host within a container. Without this
patch a call to the 'halt' inside a container will switch to the right runlevel
but finishing with 'shu
The common code between sys_socket and sys_socketat has been
grouped into the socket_create function. The both functions make
use of it.
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
---
net/socket.c | 41 -
1 file changed, 8 insertions(
This patch adds the socketat syscall which allows to specify in
which network namespace we want to create a socket. The network
namespace destination is referred by a socket fd previously opened
in the destination network namespace.
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
---
ar
This patchset (not tested) shows how it is possible to create a socket
specifying the network namespace destination. That should allow a single
process to handle several network namespaces.
--
___
Containers mailing list
[EMAIL PROTECTED]
https://lists.
Eric W. Biederman wrote:
> Thinking it over a little more I have the following thought.
>
> For binding a socket to a namespace let's use the a fd arg.
> That way we can either supply another existing network socket
> or the result of an open call. Simple, and faster if you
> are creating more th
Andreas B Aaen wrote:
> On Friday 31 October 2008 00:07, Eric W. Biederman wrote:
>> A global nsid breaks migration,
> Yes.
>
>> it breaks nested containers,
> Yes.
>
>> in general it just hurts.
> No.
>
>> So it is a bad choice for an interface.
> Not necessarily. There is a reason why vrf is
Dmitry Mishin wrote:
> Add the ability to automatically create the container fs.
> We use OpenVZ precreated template for this - these are just regular
> tarballs with all the files required for container work. So in this
> patch we just untar it into a specified root dir (and destroy one
> after co
Alexey Dobriyan wrote:
> They are bogus and should be implanted into struct net directly.
Why they are bogus ?
> In garbage collector hook, just use container_of() (once) to get struct net.
> ->dst_net is useless after that.
Yep, that looks like a better solution.
> I'm going to use this trick
The version 0.4.0 of the Linux Containers userspace tools has been released.
It is available at:
https://sourceforge.net/projects/lxc/
This version provides:
* the lxc commands can be used as a non-root user, that allows a
container to be ran without root privileges. This feature relies on t
Ian jonhson wrote:
>>> hmm then, how to configure the container to get the isolation of
>>> pid, ipc and
>>> mount points?
>> This is done automatically, with or without configuration.
>>
>> For examples:
>>
>>lxc-execute -n foo -- ps -ef --forest
>>
>> UIDPID PPID C STIME TTY
Ian jonhson wrote:
>> The container will be more or less isolated depending of what you specify in
>> the configuration file.
>>
> yes
>
>> Without any configuration file, you will have pid, ipc and mount points
>> isolated. If you specify the utsname, it will be isolated and if you specify
>> the
e are two contributions which are good examples on how to setup a
container, I added them to:
http://sourceforge.net/projects/lxc/
The first one is a chroot of a sshd server and the second one is a
minimalist debian showing a full distro booting.
> Any help?
>
> Thanks in advance.
&
; and code coverage should be significant.
>
> I.e. people running distributions that make it next to
> impossible to boot without sysfs should at be able to
> boot a test kernel now.
>
> Plus no ABIs are harmed with this patch.
>
> Signed-off-by: Eric W. Biederma
Ingo Molnar wrote:
> * Dave Hansen <[EMAIL PROTECTED]> wrote:
>
>> On Tue, 2008-10-21 at 12:21 -0700, Andrew Morton wrote:
>>> On Mon, 20 Oct 2008 01:40:28 -0400
>>> Oren Laadan <[EMAIL PROTECTED]> wrote:
These patches implement basic checkpoint-restart [CR]. This version
(v7) supports b
Oren Laadan wrote:
>
> Serge E. Hallyn wrote:
>> Quoting Daniel Lezcano ([EMAIL PROTECTED]):
>>> Oren Laadan wrote:
>>>> Daniel Lezcano wrote:
>>>>> Louis Rilling wrote:
>>>>>> On Fri, Oct 17, 2008 at 04:33:03PM -0700, Dave Hans
Oren Laadan wrote:
>
> Daniel Lezcano wrote:
>> Louis Rilling wrote:
>>> On Fri, Oct 17, 2008 at 04:33:03PM -0700, Dave Hansen wrote:
>>>> On Wed, 2008-09-03 at 14:57 +0400, Andrey Mirkin wrote:
>>>>> This patchset introduces kernel based checkpoint
Cedric Le Goater wrote:
>>> I'm afraid that we are forgetting to take the best from both
>>> approaches...
>> I agree with Louis.
>>
>> I played with Oren's patchset and tryed to port it on x86_64. I was able
>> to sys_checkpoint/sys_restart but if you remove the restoring of the
>> general registe
Dmitry Mishin wrote:
On Saturday 18 October 2008 00:42:38 Daniel Lezcano wrote:
Dmitry Mishin wrote:
On Thursday 16 October 2008 16:28:08 Daniel Lezcano wrote:
Dmitry Mishin wrote:
On Thursday 16 October 2008 13:06:45 Daniel Lezcano wrote:
Dmitry Mishin wrote:
Hi, Daniel!
Hi Dmitry ! good
Louis Rilling wrote:
> On Fri, Oct 17, 2008 at 04:33:03PM -0700, Dave Hansen wrote:
>> On Wed, 2008-09-03 at 14:57 +0400, Andrey Mirkin wrote:
>>> This patchset introduces kernel based checkpointing/restart as it is
>>> implemented in OpenVZ project. This patchset has limited functionality and
>>>
Dmitry Mishin wrote:
On Thursday 16 October 2008 16:28:08 Daniel Lezcano wrote:
Dmitry Mishin wrote:
On Thursday 16 October 2008 13:06:45 Daniel Lezcano wrote:
Dmitry Mishin wrote:
Hi, Daniel!
Hi Dmitry ! good to see you again :)
Thank you ! :)
I studied a bit lxc tools and have a couple
Daniel P. Berrange wrote:
> On Thu, Oct 16, 2008 at 02:55:23PM +0200, Cedric Le Goater wrote:
>>> Just to clarify to avoid confusion. There is a LXC project inside the
>>> libvirt and there is the lxc userspace tools (liblxc). We are talking
>>> about the liblxc.
>> I wouldn't say there is a "LXC
Dmitry Mishin wrote:
On Thursday 16 October 2008 13:06:45 Daniel Lezcano wrote:
Dmitry Mishin wrote:
Hi, Daniel!
Hi Dmitry ! good to see you again :)
Thank you ! :)
I studied a bit lxc tools and have a couple of questions. Could you
answer them?
Of course I can :)
1) Why did you chose
Oren Laadan wrote:
> Cedric Le Goater wrote:
>> Dave Hansen wrote:
>>> On Mon, 2008-10-13 at 10:13 +0200, Cedric Le Goater wrote:
hmm, that's rather complex, because we have to take into account the
kernel stack, no ? This is what Andrey was trying to solve in his patchset
back in
Alexey Eremenko wrote:
> Well, Thanks for explanation...
>
> libvirt uses liblxc or uses kernelspace containers directly ?
kernelspace containers directly.
>>> 2. What portion of code is shared between the two ?
>> I am not sure I understand the question. Do you mean : "is liblxc using
>> OpenVZ
Dmitry Mishin wrote:
Hi, Daniel!
Hi Dmitry ! good to see you again :)
I studied a bit lxc tools and have a couple of questions. Could you answer
them?
Of course I can :)
1) Why did you chose such way of a container's configuration storing? IMHO,
configuration in one file is better, becau
Alexey Eremenko wrote:
> On Tue, Oct 14, 2008 at 2:39 PM, Daniel Lezcano <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> a new version of lxc has been released.
>>
>>https://sourceforge.net/projects/lxc/
>>
>> This version takes into accou
Hi,
a new version of lxc has been released.
https://sourceforge.net/projects/lxc/
This version takes into account the control group and provides the
checkpoint / restart for external checkpoint.
It includes a lot of small improvements and fixes, full details are in
the ChangeLog file.
Dave Hansen wrote:
> On Fri, 2008-10-10 at 18:34 +0200, Greg Kurz wrote:
>> This flag is weak... testing it gives absolutly no hint whether the
>> checkpoint may succeed or not. As it is designed now, a user can only be
>> aware that checkpoint is *forever* denied. I agree that it's only useful
>>
Hi all,
I saw different emails from people asking for user space tools for the
containers, so I made a library and a set of command line tools.
This component is called "lxc" which stands for "LinuX Container".
The package can be found in the download area of:
http://sourceforge.net/projects
Dave Hansen wrote:
> These are just a few simple examples of things we know we can't
> checkpoint now. There are plenty more, but this should give
> everyone an idea how this will look in practice.
>
>
> Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
> ---
>
> linux-2.6.git-dave/fs/aio.c |
Greg Kurz wrote:
> On Thu, 2008-10-09 at 12:04 -0700, Dave Hansen wrote:
>> Suggested by Ingo.
>>
>> Checkpoint/restart is going to be a long effort to get things working.
>> We're going to have a lot of things that we know just don't work for
>> a long time. That doesn't mean that it will be usel
David Miller wrote:
> From: Daniel Lezcano <[EMAIL PROTECTED]>
> Date: Tue, 07 Oct 2008 14:07:00 +0200
>
>> Eric W. Biederman wrote:
>>> Well there is the cheap trick with this patch of waiting until the local end
>>> of veth dies.
>> I actually use ve
Mark Ryden wrote:
> Hello,
> So I wonder: the sysfs tagged directory support patch is in GerKH
> tree for more than a month.
> I cloned today latest Linus tree (2.6.27-rc9) and
> it is not there as far as I can see.
> It is also not in linux-next tree (from september).
> Now, I wonder what is the
Eric W. Biederman wrote:
> There is no good reason to not support userspace specifying the
> network namespace during device creation and it seems a handy
> thing to do.
>
> We have to be a little extra careful in this case to ensure that
> the network namespace exists through the point where we c
Eric W. Biederman wrote:
> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>
>> Perhaps, I am misunderstanding your sentence :) But just in case, let me
>> clarify
>> my idea.
>>
>> If you have a TCP connection with a send queue not empty (the kernel has
>
Eric W. Biederman wrote:
> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>
>> I agree that will make the life easier for user space developer :)
>>
>> I have a few questions about this new behaviour.
>>
>> After discussing with Benjamin, this patch means an
Eric W. Biederman wrote:
> When physical devices are inside of network namespace and that
> network namespace terminates we can not make them go away. We
> have to keep them and moving them to the initial network namespace
> is the best we can do.
>
> For virtual devices left in a network namespa
Pavel Emelyanov wrote:
> Daniel Lezcano wrote:
>> Pavel Emelyanov wrote:
>>>> Yes per namespace, I agree.
>>>>
>>>> If the option is controlled by the parent and it is done by sysctl, you
>>>> will have to make proc/sys per namespace l
Pavel Emelyanov wrote:
>> Yes per namespace, I agree.
>>
>> If the option is controlled by the parent and it is done by sysctl, you
>> will have to make proc/sys per namespace like Pavel did with /proc/net, no ?
>
> /proc/sys is already per namespace actually ;) Or what did you mean by that?
Ef
Denis V. Lunev wrote:
> On Wed, 2008-10-01 at 15:46 +0200, Daniel Lezcano wrote:
>> Denis V. Lunev wrote:
>>> On Wed, 2008-10-01 at 14:31 +0200, Daniel Lezcano wrote:
>>>> Pavel Emelyanov wrote:
>>>>>> So there are 2 cases:
>>>>&
Cedric Le Goater wrote:
> Pavel Emelyanov wrote:
>> Daniel Lezcano wrote:
>>> Pavel Emelyanov wrote:
>>>>> So there are 2 cases:
>>>>> * full isolation : restriction on VPS
>>>>> * partial isolation : no restriction but *perhaps*
Denis V. Lunev wrote:
> On Wed, 2008-10-01 at 14:31 +0200, Daniel Lezcano wrote:
>> Pavel Emelyanov wrote:
>>>> So there are 2 cases:
>>>> * full isolation : restriction on VPS
>>>> * partial isolation : no restriction but *perhaps* problem when mig
Pavel Emelyanov wrote:
>> So there are 2 cases:
>> * full isolation : restriction on VPS
>> * partial isolation : no restriction but *perhaps* problem when migrating
>>
>> Looks like we need an option per namespace to reduce the isolation for
>> af_unix sockets :)
>> - on (default): current
Denis V. Lunev wrote:
> On Wed, 2008-10-01 at 13:55 +0200, Daniel Lezcano wrote:
>> Denis V. Lunev wrote:
>>> On Wed, 2008-10-01 at 13:13 +0200, Daniel Lezcano wrote:
>>>> Denis V. Lunev wrote:
>>>>> This patch opens a way to connect via Unix socket
Denis V. Lunev wrote:
> On Wed, 2008-10-01 at 13:13 +0200, Daniel Lezcano wrote:
>> Denis V. Lunev wrote:
>>> This patch opens a way to connect via Unix socket from one namespace
>>> to another if these sockets are opened via conventional filesystem
>>> inte
Denis V. Lunev wrote:
> This patch opens a way to connect via Unix socket from one namespace
> to another if these sockets are opened via conventional filesystem
> interface. Such approach allows to share important services between
> namespaces in efficient way.
>
> This breach is controlled by th
Hi,
Greg told us last week he will retain the sysfs with namespace support
until you review them. Is there any chance you have time to look at them
this week ?
Thanks in advance
-- Daniel
___
Containers mailing list
[EMAIL PROTECTED]
https://
David Stevens wrote:
> As I've said before, I really don't like the model you're
> using for multicasting here (if I understand correctly, and
> I shamelessly admit I haven't looked at this code in detail).
Hi David,
Sorry for the delay.
> As I understand it, you're modelling the multiple virtu
xiaoming.zhang wrote:
> On Thursday 11 September 2008 11:37:33 pm Daniel Lezcano wrote:
>> xiaoming.zhang wrote:
>>> On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
>>>> In fact, after looking more closely, I see that before that message
>>&
xiaoming.zhang wrote:
> On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
>> In fact, after looking more closely, I see that before that message
>> appears: Error: unmouting old /sys
>> ERROR unmounting old /sys: Invalid argument.
>> forcing unmount of /sys
>> switchroot...
>>
>
> My exp
Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
I have exactly the same patch to be submitted :)
Acked-by: Daniel Lezcano <[EMAIL PROTECTED]>
By the way, you are posting patches related to netns. As some of us are
working in this area too, do you mi
Eelco Chaudron wrote:
> Hi All,
>
> I was looking at the network namespaces implementation for ARP, and I
> was wondering why the struct net abstraction was done in the core
> neighbour functions, and not at the struct neigh_table arp_tbl level
> (i.e. one arp_tbl per namespace)?
>
> One problem
Eelco Chaudron wrote:
> Hi Dave,
>
> Guess it's useful when you are interested in network statistics per name
> space. I'm currently evaluating how much of the name space implementation we
> could use in one of our projects (see my other email to the group).
>
> Any idea who might have a compl
David Miller wrote:
> From: Daniel Lezcano <[EMAIL PROTECTED]>
> Date: Sun, 17 Aug 2008 00:47:12 +0200
>
>> The approach looks correct except with the network namespace passed as
>> parameter, it must never be NULL.
>
> You're reviewing the patches that
Brian Haley wrote:
> Add network namespace argument to rt6_fill_node() and
> ipv6_dev_get_saddr(). This required adding a namespace pointer in the
> IPv6 fib dump callback routine.
>
> -Brian
>
> Signed-off-by: Brian Haley <[EMAIL PROTECTED]>
> ---
This patch is to fix a kernel panic in ipv6_de
Brian Haley wrote:
> Change dev_net() to handle a NULL argument - return &init_net instead.
>
> -Brian
>
> Signed-off-by: Brian Haley <[EMAIL PROTECTED]>
Did you fall into the case where the argument was NULL ?
If it is the case, I think it is not the proper way to handle that.
IMHO, this is t
Andreas B Aaen wrote:
> Whats the status of the sysfs support for namespaces? Any idea when this will
> go upstream - and through which git tree?
>
> The patches from Eric W. Biederman isn't in the tree
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
> which I have been followin
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 follo
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
Serge E. Hallyn wrote:
> Quoting Daniel Lezcano ([EMAIL PROTECTED]):
>> Serge E. Hallyn wrote:
>>> Quoting Eric W. Biederman ([EMAIL PROTECTED]):
>>>> Currently we have three possibilities on how to name pid namespaces.
>>>> - indirect via processes
Serge E. Hallyn wrote:
> Quoting Eric W. Biederman ([EMAIL PROTECTED]):
>> Currently we have three possibilities on how to name pid namespaces.
>> - indirect via processes
>> - pids
>> - names in the filesystem
>>
>> We discussed this a bit in the hallway track and pids are look like the way
>> to
Oren Laadan wrote:
> Let's have some more breakfast, tomorrow - Friday - morning.
> Same place, same time. If it doesn't rain we'll go outside ;)
>
Acked-by: Daniel Lezcano <[EMAIL PROTECTED]>
___
Containers mailin
Oren Laadan wrote:
> Hi,
>
> I've placed a somewhat more detailed summary on the wiki:
> http://wiki.openvz.org/Containers/Mini-summit_2008_notes
>
> (also accessible from: http://wiki.openvz.org/Containers/Mini-summit_2008)
>
> To further discuss technical details, let's schedule to meet while
priority
Denis Lunev : Task migration, move application on one host to another
host
Daniel Lezcano : SSI (task migration)
* Preparing the kernel internals
OL : Can we implement a kernel module and move CR functionality into
the kernel itself later ?
EB
The mini-summit agenda has been updated at:
http://wiki.openvz.org/Containers/Mini-summit_2008
Thanks.
Sauf indication contraire ci-dessus:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400
Courbev
Eric W. Biederman wrote:
> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>
>> Hi all,
>>
>> Here is a proposition a more detailed agenda for the checkpoint/restart
>> mini-summit. If everybody is ok with it, I will update the wiki.
>>
>> Comments ar
Serge E. Hallyn wrote:
> Quoting Eric W. Biederman ([EMAIL PROTECTED]):
>> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>>
>>> * Documentation
>>>* Zap : www.ncl.cs.columbia.edu/publications/usenix2007_fordist.pdf
>>>* Metacluster :
Hi all,
Here is a proposition a more detailed agenda for the checkpoint/restart
mini-summit. If everybody is ok with it, I will update the wiki.
Comments are welcome :)
Thanks
-- Daniel
The Checkpoint/restart is
Pavel Emelyanov wrote:
> David Miller wrote:
>> From: Pavel Emelyanov <[EMAIL PROTECTED]>
>> Date: Fri, 04 Jul 2008 15:58:44 +0400
>>
>>> This is the first small set of MIB statistics netnsization. The easiest
>>> case is UDP stats, so I started with this one. If this set is accepted,
>>> I will go
Tejun Heo wrote:
> Hello,
>
> Eric W. Biederman wrote:
>> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>>
>>> The kobject events are sent through a netlink message which is not
>>> currently per
>>> network namespace. Shouldn't be useful
Eric W. Biederman wrote:
> Daniel Lezcano <[EMAIL PROTECTED]> writes:
>
>> The kobject events are sent through a netlink message which is not currently
>> per
>> network namespace. Shouldn't be useful to have a way to retrieve from the
>> kobject t
Eric W. Biederman wrote:
> Tejun Heo <[EMAIL PROTECTED]> writes:
>
>> There is rather large possibility that I'm just being dumb here
>> especially because I haven't reviewed the users of this facility, so all
>> the comments I'm making are from the POV of interfaces of sysfs and the
>> related la
Tejun Heo wrote:
> Hello,
>
> Daniel Lezcano wrote:
>>> I think it would be great if sysfs_chmod_file can do all-or-nothing
>>> instead of failing half way through but given the interface of
>>> notify_change(), it could be difficult to implement. Any ide
Tejun Heo wrote:
> Hello, guys. Sorry about the long silence. Recent releases of
> popular distros overwhelmed me with ata bugs. They now seem to be
> under control (and hopefully stay that way for some time to come).
>
> On the previous iteration, I was hoping I could sort out sysfs
> interfac
FYI.
Thanks.
-- Daniel
Original Message
Subject: Re: [PATCH] iproute2: add support for IFLA_NET_NS_PID in ip link v2
Date: Mon, 23 Jun 2008 09:02:12 -0700
From: Stephen Hemminger <[EMAIL PROTECTED]>
Organization: Linux Foundation
To: Daniel Lezcano <[EMAIL
Serge E. Hallyn wrote:
> The patch looks good to me, except I'd really rename this to
> 'sysfs_tag_eq'. Calling it 'cmp', returning 't1!=t2', then checking for
> !sysfs_tag_cmp really increases the amount of thinking i have to do to
> make sure everything is koshepillager :)
>
> Maybe it's just
To be applied on top of the sysfs per namespace patchset.
___
Containers mailing list
[EMAIL PROTECTED]
https://lists.linux-foundation.org/mailman/listinfo/containers___
Devel mailing list
Devel@openvz.org
http
Pavel Emelyanov wrote:
> Hi, guys.
>
> I've recently sent a TUN devices virtualization, but it was rejected
> by Dave, since the struct net is becoming a dumping ground.
>
> I agree with him - we really need some way to register on-net data
> dynamically. That's my view of such a thing and two ex
Eric W. Biederman wrote:
> Pavel Emelyanov <[EMAIL PROTECTED]> writes:
>
>> Benjamin Thery wrote:
>>> Eric, Pavel,
>>>
>>> I haven't followed everything about the sysfs/netns issue recently and I
>>> think I have missed some of its recent developments in the past weeks.
>>> So I'm wondering what
Pavel Emelyanov wrote:
> Add the elastic array of void * pointer to the struct net.
> The access rules are simple:
>
> 1. register the ops with register_pernet_gen_device to get
> the id of your private pointer
> 2. call net_assign_generic() to put the private data on the
> struct net (m
Pavel Emelyanov wrote:
> To make some per-net generic pointers, we need some way to
> address them, i.e. - IDs. This is simple IDA-based IDs
> generator for pernet subsystems. They will be used in the
> next patches.
>
> Since it will be used by devices only (tun and vlan), I make
> it resemble th
file)
Good catch. Thanks.
Acked-by: Daniel Lezcano <[EMAIL PROTECTED]>
___
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
This patch makes the anycast and ip6_flowlabel per namespace.
--
___
Containers mailing list
[EMAIL PROTECTED]
https://lists.linux-foundation.org/mailman/listinfo/containers
___
Devel mailing list
Devel@openv
Make /proc/net/ip6_flowlabel show only flow labels belonging to the
current network namespace.
Signed-off-by: Benjamin Thery <[EMAIL PROTECTED]>
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
---
net/ipv6/ip6_flowlabel.c | 39 +++
1 file
This patch introduces a new member, fl_net, in struct ip6_flowlabel.
This allows to create labels with the same value in different namespaces.
Signed-off-by: Benjamin Thery <[EMAIL PROTECTED]>
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
---
include/net/ipv6.h |
Make use of the network namespace information to have this protocol to
handle several network namespace.
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
Signed-off-by: Benjamin Thery <[EMAIL PROTECTED]>
---
include/net/addrconf.h |3 ++-
include/net/ipv6.h | 17 ++
YOSHIFUJI Hideaki / 吉藤英明 wrote:
In article <[EMAIL PROTECTED]> (at Wed, 26 Mar 2008 00:47:42 -0700 (PDT)), David
Miller <[EMAIL PROTECTED]> says:
From: "Denis V. Lunev" <[EMAIL PROTECTED]>
Date: Wed, 26 Mar 2008 10:40:58 +0300
Commit commit c346dca10840a874240c78efe3f39acf4312a1f2
([NET] NET
Rick Jones wrote:
> Daniel Lezcano wrote:
>> Hi,
>>
>> Some performance tests was made by Benjamin to watch out the impact of
>> the network namespace. The good news is there is no impact when used
>> with or without namespaces. That has been checked using a
Hi,
Some performance tests was made by Benjamin to watch out the impact of
the network namespace. The good news is there is no impact when used
with or without namespaces. That has been checked using a real network
device inside a network namespace.
These results are consistent with the ones p
Daniel Lezcano wrote:
Denis V. Lunev wrote:
On Tue, 2008-02-19 at 10:51 +0100, Daniel Lezcano wrote:
Denis V. Lunev wrote:
On Tue, 2008-02-19 at 10:14 +0100, Daniel Lezcano wrote:
Denis V. Lunev wrote:
Default ARP parameters should be findable regardless of the context.
Required to make
Denis V. Lunev wrote:
On Tue, 2008-02-19 at 10:51 +0100, Daniel Lezcano wrote:
Denis V. Lunev wrote:
On Tue, 2008-02-19 at 10:14 +0100, Daniel Lezcano wrote:
Denis V. Lunev wrote:
Default ARP parameters should be findable regardless of the context.
Required to make inetdev_event working
Denis V. Lunev wrote:
On Tue, 2008-02-19 at 10:14 +0100, Daniel Lezcano wrote:
Denis V. Lunev wrote:
Default ARP parameters should be findable regardless of the context.
Required to make inetdev_event working.
Signed-off-by: Denis V. Lunev <[EMAIL PROTECTED]>
---
net/core/neighbour.c
Denis V. Lunev wrote:
Default ARP parameters should be findable regardless of the context.
Required to make inetdev_event working.
Signed-off-by: Denis V. Lunev <[EMAIL PROTECTED]>
---
net/core/neighbour.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/net/core/neig
301 - 400 of 621 matches
Mail list logo
