[lkml]   [2006]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: TG3 data corruption (TSO ?)
    On Mon, 2006-09-11 at 15:52 +1000, Benjamin Herrenschmidt wrote:

    > Looks like adding a sync to writel does fix it though... I'm trying to
    > figure out which specific writel in the driver makes a difference. I'll
    > then look into slicing those tcpdumps.

    During runtime in the fast path, the only writel()'s we do in tg3 are to
    the tx mbox, rx_mbox, and the interrupt mbox. The interrupt mbox
    shouldn't matter that much since it has no dependencies on other memory
    writes before it.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-09-11 18:13    [W:0.020 / U:32.648 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site