public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* UCE and NUMA
@ 2004-03-16 20:40 Mario Smarduch
  2004-03-17 16:57 ` Mario Smarduch
  2004-03-17 18:54 ` David Mosberger
  0 siblings, 2 replies; 3+ messages in thread
From: Mario Smarduch @ 2004-03-16 20:40 UTC (permalink / raw)
  To: linux-ia64

Hi,

we're currently evaluating a NUMA system (8-way). We're
wondering for hot contention spots does the 2.4 or 2.6 kernel
make use  of IA64   UCE Memory attribute (fetchadd)?
Has anyone been able to catpure relative performance
differences  (WB vs. UCE) for any benchmark ?

- Mario




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: UCE and NUMA
  2004-03-16 20:40 UCE and NUMA Mario Smarduch
@ 2004-03-17 16:57 ` Mario Smarduch
  2004-03-17 18:54 ` David Mosberger
  1 sibling, 0 replies; 3+ messages in thread
From: Mario Smarduch @ 2004-03-17 16:57 UTC (permalink / raw)
  To: linux-ia64

David Mosberger wrote:

> >>>>> On Tue, 16 Mar 2004 14:40:08 -0600, Mario Smarduch <cms063@email.mot.com> said:
>
>   Mario> Hi, we're currently evaluating a NUMA system (8-way). We're
>   Mario> wondering for hot contention spots does the 2.4 or 2.6 kernel
>   Mario> make use of IA64 UCE Memory attribute (fetchadd)?  Has anyone
>   Mario> been able to catpure relative performance differences (WB
>   Mario> vs. UCE) for any benchmark ?
>
> Note that UCE is both CPU model- and platform-specific.  Even then,
> only "fetchadd" is supported (not cmpxchg, which is what's normally
> used for spinlocks).  Furthermore, you have to be really careful to
> avoid attribute-aliasing.
>
> As long as those constraints are met, I suppose it would be OK to use
> UCE.
>
> However, is UCE really beneficial for spinlocks?  I thought it's
> primary use would be for atomic operations (such as atomic inc).
>
>         --david

 I suppose you could use fetchadd
to build some crude lockout mechanism, but probably
more useful is shared kernel data that regularly
may get updated by all CPUs (i.e. dec/inc atomically ).
That may save on WB   cache-coherency waste of bandwidth for
contentious spots.

But I agree practically it would be pretty difficult to (i) first
figure out what is very contentious (ii) and locate all your locks/data
into those UCE pages. So in short UCE is not used in any
kernel version?

- Mario


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: UCE and NUMA
  2004-03-16 20:40 UCE and NUMA Mario Smarduch
  2004-03-17 16:57 ` Mario Smarduch
@ 2004-03-17 18:54 ` David Mosberger
  1 sibling, 0 replies; 3+ messages in thread
From: David Mosberger @ 2004-03-17 18:54 UTC (permalink / raw)
  To: linux-ia64

>>>>> On Wed, 17 Mar 2004 10:57:38 -0600, Mario Smarduch <cms063@email.mot.com> said:

  Mario> But I agree practically it would be pretty difficult to (i)
  Mario> first figure out what is very contentious (ii) and locate all
  Mario> your locks/data into those UCE pages. So in short UCE is not
  Mario> used in any kernel version?

Not as far as I know.  I really don't even know which platforms
support fetchadd via UCE.

	--david

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-03-17 18:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-16 20:40 UCE and NUMA Mario Smarduch
2004-03-17 16:57 ` Mario Smarduch
2004-03-17 18:54 ` David Mosberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox