linux-kernel - Re: [Patch] mm: make CONFIG_NUMA depend on CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Jul 2011 10:49:21 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Cong Wang <amwang@...hat.com>
Cc:	Mel Gorman <mgorman@...e.de>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, Andi Kleen <andi@...stfloor.org>,
	linux-mm@...ck.org
Subject: Re: [Patch] mm: make CONFIG_NUMA depend on CONFIG_SYSFS

Le mardi 19 juillet 2011 à 15:05 +0800, Cong Wang a écrit :
> 于 2011年07月19日 14:54, Eric Dumazet 写道:
> > Le mardi 19 juillet 2011 à 14:20 +0800, Cong Wang a écrit :
> >
> >> Hmm, since we don't have to enable SYSFS for NUMA, how about
> >> make a new Kconfig for drivers/base/node.c? I.e., CONFIG_NUMA_SYSFS,
> >> like patch below.
> >>
> >
> > I dont quite understand this patch, nor the idea behind it.
> >
> > You can have a NUMA kernel (for appropriate percpu locality or whatever
> > kernel data), and yet user land processes unable to use numactl if SYSFS
> > is not enabled. I dont see a problem.
> >
> 
> Both Pekka and Mel pointed out that it makes sense to have NUMA kernel
> without SYSFS, this means sysfs interface is not a must for NUMA kernel.
> Thus, I think it makes sense to separate the numa sysfs code out.

Sorry, I misread the patch, I was confused by the title, since it still
claims "make CONFIG_NUMA depend on CONFIG_SYSFS" ;)



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/