* H. Peter Anvin <hpa@zytor.com> wrote:hm, can it result in a broken kernel? If yes, how? Or are your objections more higher level? i actually like that we end up with something rather NOP-ish, with some mild 'ambient' impact due to the extra constraints that state value visibility brings with it. The in-source impact of the markers is minimal, especially with Peter Zijstra's wrappers. The scheduler markers at least are also expected to stay pretty stable as well. the syscall markers should be done less intrusively - and i think they can be done less intrusively. but we need to get past this current impasse, the optimizations that Mathieu has done to markers are pretty impressive so far. The overhead is not zero, but it gets quite close to it and the SystemTap and kprobes people are happy with it as well. it would clearly fall under the Fair Use Doctrine and perhaps also under the Doctrine of Severe Necessities, so dont be shy! Ingo --
| H. Peter Anvin | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Alex Chiang | [PATCH 1/4] Remove path attribute from sgi_hotplug |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Eric Dumazet | Re: [PATCH 3/3] Convert the UDP hash lock to RCU |
