[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C110EDD.2010409@kernel.org>
Date: Thu, 10 Jun 2010 18:12:13 +0200
From: Tejun Heo <tj@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>
CC: linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
Colin Tuckley <colin.tuckley@....com>,
Jeff Garzik <jeff@...zik.org>
Subject: Re: [PATCH v2] sata_sil24: Use memory barriers before issuing commands
On 06/10/2010 06:02 PM, Catalin Marinas wrote:
> The data in the cmd_block buffers may reach the main memory after the
> writel() to the device ports. This patch introduces two calls to wmb()
> to ensure the relative ordering.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@....com>
> Tested-by: Colin Tuckley <colin.tuckley@....com>
> Cc: Tejun Heo <tj@...nel.org>
> Cc: Jeff Garzik <jeff@...zik.org>
I suppose you have tested and verified that this is actually
necessary, right? I've been looking through the docs but couldn't
find anything which described the ordering between writes to main
memory and write[bwl]()'s. One thing that kind of bothers me is that
r/wmb()'s are for ordering memory accesses among CPUs which
participate in cache coherency protocol and although it may work right
in the above case I'm not really sure whether this is the right thing
to do. Do you have more information on the subject?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists