Re: XL driver checksum producing corrupted but checksum-correct packets

From: Luigi Rizzo (rizzo_at_icir.org)
Date: 01/25/04

  • Next message: Robert Watson: "Re: XL driver checksum producing corrupted but checksum-correct packets" 
    Date: Sat, 24 Jan 2004 15:10:29 -0800
To: Robert Watson <rwatson@freebsd.org>

    On Sat, Jan 24, 2004 at 02:12:12PM -0500, Robert Watson wrote:
    ...
    > > but going this way you have no idea on what the driver does, including
    > > enabling hw checksums. This looks like a useless test at least for the
    > > purpose of finding out what is going wrong
    >
    > Actually, I'm more curious about whether it's a known errata/misbehavior
    > for the card that 3Com's drivers work around, or not. The problem could
    > well be compleely unrelated to hardware checksuming per se -- the
    > corruption might well be taking place as the buffer is moved from the
    > card's buffer to the operating system managed buffer. If the NDIS driver
    > doesn't illustrate the same problem, it tells us that by frobbing
    > appropriately, this problem can be worked around. It also tells us that
    > by looking a bit harder at what the driver is doing (i.e., how it frobs
    > the hardware), we can learn something about the appropriate workaround.

    yes, but how would you know that, short of reverse engineering
    the driver, or tracing I/O accesses to the hardware ?
    It really looks like an overkill effort... I'd rather just
    try to debug the issue working on an open source driver, or
    dump the hardware altogether and replace it with something
    known to work...

            cheers
            luigi
    _______________________________________________
    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: Robert Watson: "Re: XL driver checksum producing corrupted but checksum-correct packets"

    Relevant Pages

    • [PATCH 29/30] W1: Documentation/w1/masters/ds2490 update
      ... Provide some additional details about the status of the driver and the ... +- While the ds2490 supports a hardware search the code doesn't take ... a write buffer and a read buffer as arguments. ... the bulk read will return an error and the hardware will ...
      (Linux-Kernel)
    • Re: [PATCH 29/30] W1: Documentation/w1/masters/ds2490 update
      ... Provide some additional details about the status of the driver and the ... +- While the ds2490 supports a hardware search the code doesn't take ... a write buffer and a read buffer as arguments. ... the bulk read will return an error and the hardware will ...
      (Linux-Kernel)
    • [PATCH 29/30] W1: Documentation/w1/masters/ds2490 update
      ... Provide some additional details about the status of the driver and the ... +- While the ds2490 supports a hardware search the code doesn't take ... a write buffer and a read buffer as arguments. ... the bulk read will return an error and the hardware will ...
      (Linux-Kernel)
    • Re: Difference between synchronous and asynchronous operation/calls (NDISPROT)
      ... The main problem with synchronous operation/calls seems to be the lack of buffers for the driver to store data into. ... Each "read call" supplies the driver with a buffer and optionally a completion routine so that the driver can inform the application when the requested operation is/was done. ... However it seems the current windows/driver design does some copies as well? ...
      (microsoft.public.development.device.drivers)
    • Re: Degradation of TCP connection
      ... Gigabit ethernet. ... D card's data buffer can only hold about 64K samples worth of data ... link you posted is for an older version of VxWorks that used a BSD- ... but a bug in the ethernet driver. ...
      (comp.os.vxworks)