public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Erik Jacobson <erikj@sgi.com>,
	guillaume.thouvenin@bull.net, linux-kernel@vger.kernel.org,
	zaitcev@redhat.com
Subject: Re: [PATCH] connector: Some fixes for ia64 unaligned access errors
Date: Mon, 11 Dec 2006 17:29:07 -0800	[thread overview]
Message-ID: <20061211172907.305473cf.zaitcev@redhat.com> (raw)
In-Reply-To: <1165881167.24721.73.camel@localhost.localdomain>

On Mon, 11 Dec 2006 15:52:47 -0800, Matt Helsley <matthltc@us.ibm.com> wrote:

> 	I'm shocked memcpy() introduces 8-byte stores that violate architecture
> alignment rules. Is there any chance this a bug in ia64's memcpy()
> implementation? I've tried to read it but since I'm not familiar with
> ia64 asm I can't make out significant parts of it in
> arch/ia64/lib/memcpy.S.

The arch/ia64/lib/memcpy.S is probably fine, it must be gcc doing
an inline substitution of a well-known function.

A commenter on my blog mentioned seeing the same thing in the past.
(http://zaitcev.livejournal.com/107185.html?thread=128945#t128945)

It's possible that applying (void *) cast to the first argument of memcpy
would disrupt this optimization. But since we have a well understood
patch by Erik, which only adds a penalty of 32 bytes of stack waste
and 32 bytes of memcpy, I thought it best not to bother with heaping
workarounds.

-- Pete

  reply	other threads:[~2006-12-12  1:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 23:22 [PATCH] connector: Some fixes for ia64 unaligned access errors Erik Jacobson
2006-12-09  3:20 ` Pete Zaitcev
2006-12-09  7:47   ` Matt Helsley
2006-12-09 21:09   ` Erik Jacobson
2006-12-10  2:34     ` Pete Zaitcev
2006-12-11 23:52       ` Matt Helsley
2006-12-12  1:29         ` Pete Zaitcev [this message]
2006-12-12  1:50           ` David Miller
2006-12-12  3:09             ` Matt Helsley
2006-12-12  3:41               ` David Miller
2006-12-12  2:07           ` Chen, Kenneth W
2006-12-11 23:52 ` Matt Helsley
2006-12-12 17:54   ` Erik Jacobson
2006-12-13  0:45     ` Andrew Morton
2006-12-13  2:31       ` Erik Jacobson
2006-12-13  2:38         ` Andrew Morton
2006-12-13  6:08           ` Erik Jacobson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061211172907.305473cf.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=erikj@sgi.com \
    --cc=guillaume.thouvenin@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox