Messages in this thread | | | Subject | Re: [PATCH] Use uname not sysctl to get the kernel revision | From | Arjan van de Ven <> | Date | Thu, 13 Jul 2006 17:05:18 +0200 |
| |
On Thu, 2006-07-13 at 08:39 -0600, Eric W. Biederman wrote: > Ulrich Drepper <drepper@redhat.com> writes: > > > Eric W. Biederman wrote: > >> Ulrich what would be interesting besides the possibility of having > >> multiple cpus? > > > > What is needed for various things like memory handling etc is all > > topology information. Somebody might remember the numa library proposal > > I had in April 2004 which was cast aside because people were only > > looking for a "quick fix". Well, the problem still isn't solved. > > > > IMO the vdso should export information about: > > > > - processors and their relationship (hyperthreads, cores) > > > > - the CPU caches and how they relate to the cores (e.g., dual core > > with shared L2) > > > > - local main memory for each processor > > > > - relative costs of the memory access of the various memory regions > > (for numa local memory to a node, intra-node costs) > > > > - ideally, relative costs main memory and CPU caches > > > > > > All this information can be steadily updated by the kernel as new > > CPUs/memory get added/removed. The vdso should have functions to access > > this information. It's easy enough to make this access race free. > >
why does this have to be in the vdso? It's not like the code can be a regular userspace lib/daemon that gets all the hotplug events and that processes the info from /proc and /sys once during boot. A bit like how nscd works I suppose..
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |