Messages in this thread | | | Subject | Re: 2.6.11-rc1-mm1 | From | Thomas Gleixner <> | Date | Sat, 15 Jan 2005 10:57:12 +0100 |
| |
Hi Karim,
On Fri, 2005-01-14 at 20:14 -0500, Karim Yaghmour wrote: > Gee Thomas, I guess you really want to take this one until the last > man is standing. Feel free to use the ad-hominem tone if it suits > you. Don't hold it against me though if I don't bite :)
No personal offence was intended.
> Thomas Gleixner wrote: > > It's not only me, who needs constant time. Everybody interested in > > tracing will need that. In my opinion its a principle of tracing. > > relayfs is a generalized buffering mechanism. Tracing is one application > it serves. Check out the web site: "high-speed data-relay filesystem." > Fancy name huh ...
I do not doubt that.
But hardwiring an instrumentation framework on it is also hardwiring implicit restrictions on the usability of the instrumentation for certain purposes.
> > The "lockless" mechanism is _FAKE_ as I already pointed out. It replaces > > locks by do { } while loops. So what ? > > Well for one thing, a portion of code running in user-context won't > disable interrupts while it's attempting to get buffer space, and > therefore won't impact on interrupt delivery.
The do {} while loops are in the fast ltt_log_event path
> Clearly you haven't read the implementation and/or aren't familiar with > its use. Usually, what you want to do is open(), mmap(), write(), there > is no "conversion" to a file. The filesystem abstraction is just a > namespace holder for us.
I have read it and tried it. I don't see a point why I can't map a ringbuffer into user space. I'm not beating on the ringbuffer, but I'm using it as an example. :)
> That's not the point. You're bending backwards as far as you can reach > trying to raise as much mud as you can, but when pressed for actual > constructive input you hide behind a strawman argument. If you don't > have anything to say, then stop whining.
I gave constructive criticism along with points, where I just point on the restrictions and weakness of the implementation.
tglx
- 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/
| |