In-Reply-To: <20051012023950.5261.qmail@science.horizon.com>
References: <20051012023950.5261.qmail@science.horizon.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <678DF2CB-3842-4801-9A86-787957CB3DDF@mac.com>
Cc: cfriesen@nortel.com, dev@sw.ru, linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 7bit
From: Kyle Moffett <mrmacman_g4@mac.com>
Subject: Re: SMP syncronization on AMD processors (broken?)
Date: Tue, 11 Oct 2005 23:27:33 -0400
To: linux@horizon.com
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1972
Lines: 45

On Oct 11, 2005, at 22:39:50, linux@horizon.com wrote:
>> This may work on some processors, but on others the read of  
>> "progress" in XXX, or the write in YYY may require arch-specific  
>> code to force the update out to other cpus.
>>
>> Alternately, explicitly atomic operations should suffice, but a  
>> simple increment is probably not enough for portable code.
>
> Er.. you mean, the pre-incremented value could be cached  
> *indefinitely* by XXX?  That seems odd...
>
> I can see an arch hook (memory barrier sort of thuing) to push it  
> out a bit faster, but are there architecures on which noticing the  
> increment could be delayed indefinitely?
>
> In particular, that same hook would already be used by the spin  
> lock release sequence (to ensure that someone else notices the lock  
> is now available), and unless it's address-specific, it would do  
> for the "progress" counter as well.

Umm, IIRC, some architectures (don't remember which ones, but I'd  
guess it's the big 512-way boxen) have cache-line-and-memory models  
such that a cacheline may remain out-of-date indefinitely unless the  
CPU with the update runs a "cache-line flush" instruction or the CPU  
who wants an update requests one with an exclusive cacheline lock or  
similar.  On such a system, the only way to ensure safe distribution  
of data between CPUs is to make sure it's in the same cacheline as  
the spinlock (and document that fact) or use special instructions to  
verify coherency.

Cheers,
Kyle Moffett

--
Debugging is twice as hard as writing the code in the first place.   
Therefore, if you write the code as cleverly as possible, you are, by  
definition, not smart enough to debug it.
   -- Brian Kernighan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/