X86: Any reason why `CONFIG_NUMA` is disabled for x86 but enabled for some arm devices like layerscape?

[vincejv]

Asking so I can submit a PR to resolve this, Numa nodes is especially useful for x86 esp on multiprocessor/core systems with docker, and it's already enabled on ARMSR, so why not x86?

Correction: Not ARMSR, but some arm devices like layerscape

[vincejv]

CONFIG_EXT4_FS_POSIX_ACL
CONFIG_EXT4_FS_SECURITY

also disabled for x86 but enabled on ARMSR, these are needed for setcap which a docker/lxc container may use, do we really need to disable these functionalities in x86 which flash space isn't an issue??

Setcap (libcap) - Failed to set capabilities on file: Not supported

CONFIG_KERNEL_EXT4_FS_SECURITY=y is needed for setcap/setxattr "security.capability" namespace prefix. strace shows: setxattr("/bin/chrt", "security.capability", "\1\0\0\2\0\1\0\0\0\1\0\0\0\0\0\0\0\0\0", 20, 0) = -1 EOPNOTSUPP (Not supported) setxattr(2) says: ENOTSUP The namespace prefix of name is not valid. ENOTSUP Extended attributes are not supported by the filesystem, or are disabled

Correction: Not ARMSR, but some arm devices like layerscape