Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32

    Bryan> I'll take a look at whether the extra call/ret indirection
    Bryan> affects performance in a measurable fashion.

Your current implementation is out-of-line, right?

I would be surprised if calling a function has any overhead on x86_64,
since the function call is a jump that can be predicted perfectly.
The only issue is the code to shuffle values into the right registers.

 - R.
-
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 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>

• References:
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Roland Dreier <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Christoph Hellwig <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Christoph Hellwig <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Sam Ravnborg <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    • From: "Bryan O'Sullivan" <[email protected]>

• Prev by Date: Re: 2.6.15-mm3
• Next by Date: Re: Is user-space AIO dead?
• Previous by thread: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
• Next by thread: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
• 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]