RE: [PATCH] pch_gbe: Adding read memory barriers
From: David Laight
Date: Wed May 09 2012 - 06:48:37 EST
> Under a strong incoming packet stream and/or high cpu usage,
> the pch_gbe driver reports "Receive CRC Error" and discards packet.
> It occurred on an Intel ATOM E620T while running a
> 300mbit/sec multicast
> network stream leading to a ~100% cpu usage.
> Adding rmb() calls before considering the network card's status solve
> this issue.
> Getting it into stable would be perfect as it solves
> reliability issues.
> Signed-off-by: Erwan Velu <erwan.velu@xxxxxxxxxxxxxxxxxxx>
> .../net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
> diff --git a/drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c
> index 8035e5f..ace3654 100644
> --- a/drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c
> +++ b/drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c
> @@ -1413,6 +1413,7 @@ static irqreturn_t pch_gbe_intr(int
> irq, void *data)
> + smp_rmb(); /* prevent any other reads before*/
Under the assumption that your memory references are uncached,
you only need to stop gcc reordering the object code,
Rather than actually adding one of the 'fence' instructions.
So you should only need: asm volatile(:::"memory")
NFI which define generates that, the defines in the copy of
sysdep.h I just looked at always include one of the fences.
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/