On Fri, Sep 29, 2006 at 09:50:37AM -0400, [EMAIL PROTECTED] wrote: > System Administrators are probably more accustomed to well-known > tools like ethereal/snoop/tcpdump that allows them to filter above > info out from the wire. Are we trying to find out if/why the packet > got all the way to ip's send routine, but didn't make it out to the wire? > IOW info like the following:
I think the "threading the packet processing" idea is something that someone interested in seeing _how_ Solaris handles TCP/IP will be interested in. But when you're trying to solve actual problems I suspect it'll be something else that one needs. BTW, is there some key that one can use as a key to an associative array to track a single tcp "output" down to the network layer? Some sort of packet ID or STREAMS message ID, or something of the sort? I really think that threading packet processing is just not a well- thought out feature and not necessarily easy to implement with the current infrastructure. I don't think the project team should be burdened with adding it. Folks who need such tracing can rely on higher-cost associative arrays and/or unstable fbt probes. _______________________________________________ networking-discuss mailing list [email protected]
