search for: fireengine

I''ve been thinking about hardware that has multiple transmit rings ("tx resources"). We really should have a way to expose this up to the stack. And ideally, the stack should guarantee that a given flow will always be sent down using the same hardware tx resource. I''ve heard that crossbow will deliver this, but I can''t find evidence of it in the crossbow

I am trying to use dtrace to trace all sscanf calls. I am able to use pid provider for this. But my application forks off children at times to handle requests. Is there a way I can stop the child process immediately after it is started so that I can attach a pid provider to that and trace the scanf calls in it? I have tried using the "create" probe but that did not help.

> There are times when arg0 can be NULL [for the interrupt-start or > interrupt-complete probe] if there''s no associated device. > There''s already a bug open to address the error in the documentation. > 6284911 args to interrupt-start and interrupt-complete need more info Hmm, I noticed that, too. There''s currently a thread on yahoo''s solarisx86