Re: [PATCH 6/24] make atomic_read() behave consistently on frv

Chris Snook <[email protected]> wrote:

> To head off the criticism, I admit this is an oversimplification, and true
> busy-waiters should be using cpu_relax(), which contains a barrier.

Why would you want to use cpu_relax()?  That's there to waste time efficiently,
isn't it?  Shouldn't you be using smp_rmb() or something like that?

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

---

• Follow-Ups:
  • Re: [PATCH 6/24] make atomic_read() behave consistently on frv
    • From: David Howells <[email protected]>
  • Re: [PATCH 6/24] make atomic_read() behave consistently on frv
    • From: Chris Snook <[email protected]>

• References:
  • Re: [PATCH 6/24] make atomic_read() behave consistently on frv
    • From: Chris Snook <[email protected]>
  • [PATCH 6/24] make atomic_read() behave consistently on frv
    • From: Chris Snook <[email protected]>

• Prev by Date: Re: + sysctl-error-on-bad-sysctl-tables.patch added to -mm tree
• Next by Date: Re: + sysctl-remove-binary-sysctl-support-where-it-clearly-doesnt-work.patch added to -mm tree
• Previous by thread: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
• Next by thread: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]