On Mon, 17 Sep 2007, Lee Schermerhorn wrote:
> Only for vma policy, right? show_numa_maps() isn't a performance path,
> and shared policies are already reference counted--just not unref'd!
Right.
> I do have some ideas for enhancements to memtoy to test vma policies in
> a multi-threaded task. I have the basic multi-threading infrastructure
> that binds threads to cpus, allocates node local stacks, thread state
> structs, ... in my mmtrace tool that I can probably hack for use in
> memtoy to provoke cacheline bouncing of the mem policy. But, if pft
> does the trick, I won't rush the memtoy enhancments...
Well pft is old and limited in what it can do. I'd be glad if you could
put it into memtoy. Then it may perhaps be useful in the future.
> Meanwhile, we do have a mem policy ref counting bug in the mainline.
But we have had this ref counting issue forever with no ill effect. Memory
policies were designed to have almost no overhead for the default
allocation paths. Incrementing and decrementing refcounters makes that
design no longer light weight as it was intended to be.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
