Re: [PATCH 3/3] C/R: Basic support for network namespaces and devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OL> Would this compile without CONFIG_NET ?  without CONFIG_NET_NS ?

Nope, but it does depend on CONFIG_CHECKPOINT, of course.  I'll add
some Kconfig magic to try to straighten that out.

OL> How can a user ask to not checkpoint the network-ns ?  (e.g. in
OL> a subtree checkpoint)

Do we really want to start adding fine-grained control over everything
that we checkpoint?  Can you ask it to not checkpoint the ipc_ns,
uts_ns, etc?  The previous example of this was connected sockets,
which I think is different, given the potential for a long delay
before restart ensuring the sockets will be dead anyway.

OL> Is there a reason not to collect all addresses into one buffer
OL> (can there be more than a page worth of them ?) and write in one
OL> go ?

I don't really see anywhere that the list is bounded.  I'd say that in
most cases each interface will only have one address anyway.

-- 
Dan Smith
IBM Linux Technology Center
email: danms@xxxxxxxxxx
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers

[Index of Archives]     [Cgroups]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux