Daniel Golle <dan...@makrotopia.org> [2018-12-29 06:51:32]:

>  config KERNEL_AIO
>  config KERNEL_FHANDLE
>  config KERNEL_FANOTIFY
> +     default y if !SMALL_FLASH

What about `FEATURES += nas` to make it clear and don't abuse SMALL_FLASH.

>  config KERNEL_CGROUPS
>  config KERNEL_CPUSETS
>  config KERNEL_CGROUP_CPUACCT
>  config KERNEL_RESOURCE_COUNTERS
>  config KERNEL_MEMCG
>  config KERNEL_MEMCG_KMEM
>  menuconfig KERNEL_CGROUP_SCHED
>   config KERNEL_FAIR_GROUP_SCHED
>   config KERNEL_RT_GROUP_SCHED
>  config KERNEL_NAMESPACES
>  config KERNEL_LXC_MISC
>  config KERNEL_SECCOMP_FILTER
>  config KERNEL_SECCOMP
> -             default n
> +             default y if !SMALL_FLASH

What about `FEATURES += containers` ?

Daniel Engberg <daniel.engberg.li...@pyret.net> [2018-12-30 10:21:46]:

> however KERNEL_CGROUPS, config KERNEL_NAMESPACES, config KERNEL_LXC_MISC,
> KERNEL_SECCOMP_FILTER are very limited use cases to my knowledge and more or
> less only used on x86*?

There are other quite powerful platforms like mvebu, imx6, ipq etc. where you
could use this as well.

-- ynezz

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to