Re: intermittant petabyte usage reported with broadcom nic

From: Roland Dreier
Date: Thu Apr 12 2007 - 19:16:13 EST

Next message: David Miller: "Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt opscallsites to make them patchable"
Previous message: Dmitry Adamushko: "[PATCH] [DEBUG] sd-sched: monitor dynamic priority levels of a running task"
In reply to: CaT: "Re: intermittant petabyte usage reported with broadcom nic"
Next in thread: Roland Dreier: "Re: intermittant petabyte usage reported with broadcom nic"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Apr 9 06:19:04 ' eth0:14250798570591813804 2284720007938 18638 0 0 18638 0 27375938 1556640980159 3345714490 0 0 0 0 0 0 '

One odd thing is that crazy number 14250798570591813804 is
c5c501cbc5c500ac in hex. I dunno what the significant of the 0xc5 bit
pattern is though...

The other line has 220898233988841368, which is 0x310c9c6006a7f98, not
nearly so regular a patter.

I don't think I'm helping much...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: David Miller: "Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt opscallsites to make them patchable"
Previous message: Dmitry Adamushko: "[PATCH] [DEBUG] sd-sched: monitor dynamic priority levels of a running task"
In reply to: CaT: "Re: intermittant petabyte usage reported with broadcom nic"
Next in thread: Roland Dreier: "Re: intermittant petabyte usage reported with broadcom nic"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]