On Wed, 2006-01-11 at 10:49 -0800, Roland Dreier wrote: > Your current implementation is out-of-line, right? The memcpy32 routine is, but __raw_memcpy_toio32 simply calls it, so we have two jump/ret pairs instead of one. > 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. Indeed. <b - 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: Roland Dreier <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- 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]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- From: Roland Dreier <[email protected]>
- Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- Prev by Date: Re: Is user-space AIO dead?
- Next by Date: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
- 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):
 |