Re: [PATCH] pch_gbe: Adding read memory barriers
From: Ben Hutchings
Date: Wed May 09 2012 - 11:39:20 EST
On Wed, 2012-05-09 at 17:20 +0200, Erwan Velu wrote:
> Thanks for this very clear description.
It might be clear, but it's not very relevant: you need to understand
the Linux kernel barrier APIs (which cover all architectures). See
> As I'm pretty new to this kind of integration in the kernel, do you
> request me to test this volatile option ?
> Does the patch tends to be rejected for this issue ?
> What should be the next step for my patch ?
Explain what kind of reordering you are trying to avoid.
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
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/