Re: [PATCH -mm] i386 syscall opcode reordering (pipelining)

Andreas Mohr wrote:

Hi all,

I'd guess that this version features improved pipeline parallelism,
since we isolate competing %ebx accesses (_syscall4()) and
stack push operations (_syscall5()), right?

is anybody actually EVER using those???
I would think not....
-
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 -mm] i386 syscall opcode reordering (pipelining)
    • From: Andreas Mohr <[email protected]>
  • Re: [PATCH -mm] i386 syscall opcode reordering (pipelining)
    • From: "H. Peter Anvin" <[email protected]>

• References:
  • [PATCH -mm] i386 syscall opcode reordering (pipelining)
    • From: Andreas Mohr <[email protected]>

• Prev by Date: Re: [RFC] Slimming down struct inode
• Next by Date: Re: [PATCH -mm] i386 usercopy.c opcode reordering (pipelining)
• Previous by thread: [PATCH -mm] i386 syscall opcode reordering (pipelining)
• Next by thread: Re: [PATCH -mm] i386 syscall opcode reordering (pipelining)
• 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]