> I'm not sure a hardware solution is even the right thing - consider a
> shared memory database process with a private heap. You really want
> locks on the shared memory, and you really don't on the heap.
>
> You need a way to type the lock semantics by memory region, and a
> working hardware solution can not perform as well as a careful software
> solution. As was pointed out earlier, you can't use memory type
The problem is that nobody will change all the software.
Your careful software solution will only benefit a small
minority of performance conscious and well tuned programs.
The hardware solution might not be perfect, but has a good chance
to apply to 90% of the "don't care" programs and help them all a bit.
And every bit counts in the quest for more single thread performance.
And if someone wants to fine tune their programs they can
still change the software as much as they want.
-Andi
-
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]
