[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Improving the data supplied by BPF
>> I wasn't proposing an interface to control tap location, just
>> flag bits to record what happened. I once added support to
>> ath(4) to do the tapping on tx complete so it could include more
>> status. But I see the point that one has to stop somewhere.
It would be very nice to be able to annotate where the tap was.
I've often shoved data into the bpf system from unusual places as a
>>>>> "Darren" == Darren Reed <darrenr%netbsd.org@localhost> writes:
Darren> I wonder if what you're looking for is something more akin
Darren> to what dtrace allows? bpf's purpose is primarily packet
Darren> data and not so much NIC status, etc. A dtrace-like solution
Darren> would let you tap packets as they move along, in and out of
Darren> packets and at specific "probe" points. I say that because
Darren> it sounds like you are just as (if not more) interested in
Darren> non-packet data and for that, I think BPF is not really the
Darren> right answer...
uhm. yeah, dtrace-ish, but really, that's too programmer oriented I
think, even if under the hood that's the right implementation.
] Y'avait une poule de jammé dans l'muffler!!!!!!!!! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr%sandelman.ottawa.on.ca@localhost http://www.sandelman.ottawa.on.ca/
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
Main Index |
Thread Index |