sysctl variables are not available to newly created namespace
G, Madhukrishna
madhukrishna.g at hpe.com
Wed Jul 27 11:10:36 UTC 2016
Hi,
In my current linux 3.2.71 stable version , I have created a network namespace and when I listed sysctl variables in following directory " /proc/sys/net/core/" am able to see net.core.xfrm* variables only, i.e only CONFIG_SYSCTL related variables, even though I have enabled CONFIG_NET as well as CONFIG_NET_NS I am not able to see any sysctl variables related to ne.core(rmem_max, wmem_max, rmem_default and wmem_default).
#<mailto:root at ned4g8:/home/gmadhuk/linux-3.16-clim-3.16.7-clim#> ip netns exec gmk1 ls -l /proc/sys/net/core/
total 0
-rw-r--r-- 1 root root 0 Jul 25 03:01 somaxconn
-rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_acq_expires
-rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_aevent_etime
-rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_aevent_rseqth
-rw-r--r-- 1 root root 0 Jul 25 03:01 xfrm_larval_drop
Where as in my older kernel version, it will show all sysctl variables.
# ls -l /proc/sys/net/core/
total 0
-rw-r--r-- 1 root root 0 Jul 20 05:40 busy_poll
-rw-r--r-- 1 root root 0 Jul 20 05:40 busy_read
-rw-r--r-- 1 root root 0 Jul 20 05:40 default_qdisc
-rw-r--r-- 1 root root 0 Jul 20 05:40 dev_weight
-rw-r--r-- 1 root root 0 Jul 20 05:40 flow_limit_cpu_bitmap
-rw-r--r-- 1 root root 0 Jul 20 05:40 flow_limit_table_len
-rw-r--r-- 1 root root 0 Jul 20 05:40 message_burst
-rw-r--r-- 1 root root 0 Jul 20 05:40 message_cost
-rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_budget
-rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_max_backlog
-rw-r--r-- 1 root root 0 Jul 20 05:40 netdev_tstamp_prequeue
-rw-r--r-- 1 root root 0 Jul 20 05:40 optmem_max
-rw-r--r-- 1 root root 0 Jul 20 05:40 rmem_default
-rw-r--r-- 1 root root 0 Jul 20 05:40 rmem_max
-rw-r--r-- 1 root root 0 Jul 20 05:40 rps_sock_flow_entries
-rw-r--r-- 1 root root 0 Jul 20 05:40 somaxconn
-rw-r--r-- 1 root root 0 Jul 20 05:40 warnings
-rw-r--r-- 1 root root 0 Jul 20 05:40 wmem_default
-rw-r--r-- 1 root root 0 Jul 20 05:40 wmem_max
-rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_acq_expires
-rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_aevent_etime
-rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_aevent_rseqth
-rw-r--r-- 1 root root 0 Jul 20 05:40 xfrm_larval_drop
Please furnish me how I can avoid such things.
Thanks in Advance.
Regards
25krishna
More information about the Containers
mailing list