RE: memory mapped packet capturing - bpf replacement ?

From: Ed Maste (emaste_at_sandvine.com)
Date: 06/18/04

  • Next message: Don Bowman: "RE: memory mapped packet capturing - bpf replacement ?"
    To: freebsd-hackers@freebsd.org
    Date: Fri, 18 Jun 2004 13:25:51 -0400
    
    

    Matthew Dillon wrote:
    >
    > There's no reason why the time has to be in microseconds or
    > even that it must be adjusted to realtime. You also do not
    > have to support low power modes during testing which means
    > that just time-stamping the packets with the TSC plus a simple
    > base offset to correct for variences between cpus and machines
    > on the network ought to be sufficient.

    Fair enough. In my case I didn't need the timestamp anyway
    so just disabling it was the least-effort way to remove the
    overhead.

    I pointed out the timestamp issue only because it will penalize
    BPF against a new method (that doesn't have them) more than one
    might expect.

    -ed
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


  • Next message: Don Bowman: "RE: memory mapped packet capturing - bpf replacement ?"

    Relevant Pages

    • RE: System Failure Stop Error
      ... unexpected shutdown of this computer is: System Failure: Stop error ... Reason Code: 0x805000f ... | Timestamp: unavailable ...
      (microsoft.public.windows.server.sbs)
    • Re: File cache effecting access time...
      ... > The reason I ask is I want to test my hypothesis that ... > the 'last accessed' timestamp is not refreshed when a file is cached... ... "Note Not all file systems can record creation and last access time and not ... access time has a resolution of 1 hour. ...
      (microsoft.public.win32.programmer.kernel)
    • System Failure Stop Error
      ... The reason supplied by user EVENTS\Administrator for the last ... Frame IP not in any known module. ... Timestamp: unavailable ... Checksum: 00000000 ...
      (microsoft.public.windows.server.sbs)
    • Re: Extended-Precision Division
      ... specifically I am taking a timestamp from rdtsc and converting it into microseconds. ... First I have to multiply by 1,000,000 to get a temporary 96-bit product, and then I can divide by the CPU frequency. ... It does not hurt to have too much precision, so I am using microseconds for my counter. ...
      (comp.lang.asm.x86)
    • Re: Subtracting Microseconds from Timestamp
      ... This timestamp form doesn't contain ... accordingly in microseconds or nanoseconds. ... dn> query is 80192300. ... If you need to get interval between two queries, ...
      (comp.unix.programmer)