Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.

> Something like that had to be done eventually about the inefficient
> current_thread_info() mechanism, 

Inefficient? It's two fast instructions. I won't call that inefficient.

> I guess it's due to having tried that on an older installation with gcc 3.2,
> which probably does less efficient opcode merging of current_thread_info()
> requests compared to a current gcc version.

gcc normally doesn't merge inline assembly at all.

-Andi
-
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 RFC 0/6] Implement per-processor data areas for i386.
    • From: Andreas Mohr <[email protected]>

• References:
  • [PATCH RFC 0/6] Implement per-processor data areas for i386.
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.
    • From: Andreas Mohr <[email protected]>

• Prev by Date: Re: LogFS
• Next by Date: Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.
• Previous by thread: Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.
• Next by thread: Re: [PATCH RFC 0/6] Implement per-processor data areas for i386.
• 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]