Date: Sat, 17 Dec 2005 19:19:32 -0800
From: Andrew Morton <akpm@osdl.org>
To: Robert Walsh <rjwalsh@pathscale.com>
Cc: rolandd@cisco.com, linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 03/13]  [RFC] ipath copy routines
Message-Id: <20051217191932.af2b422c.akpm@osdl.org>
In-Reply-To: <1134859243.20575.84.camel@phosphene.durables.org>
References: <200512161548.HbgfRzF2TysjsR2G@cisco.com>
	<200512161548.lRw6KI369ooIXS9o@cisco.com>
	<20051217123833.1aa430ab.akpm@osdl.org>
	<1134859243.20575.84.camel@phosphene.durables.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1160
Lines: 36

Robert Walsh <rjwalsh@pathscale.com> wrote:
>
> > > +	movl %edx,%ecx
> > > +	shrl $1,%ecx
> > > +	andl $1,%edx	
> > > +	cld
> > > +	rep 
> > > +	movsq 
> > > +	movl %edx,%ecx
> > > +	rep
> > > +	movsd
> > > +	ret
> > 
> > err, we have a portability problem.
> 
> Any chance we could get these moved into the x86_64 arch directory,
> then?

That would make sense.  Give it a non-ipath-related name and require that
all architectures which wish to run this driver must implement that
(documented) function.

And, in Kconfig, make sure that architectures which don't implement that
library function do not attempt to build this driver.  To avoid breaking
`make allmodconfig'.

>  We have to do double-word copies, or our chip gets unhappy.

In what form is this chip available?  As a standard PCI/PCIX card which
people will want to plug into power4/ia64/x86 machines?  Or is it in some
way exclusively tied to x86_64?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/