[lkml]   [2000]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] string-486.h modified
Jamie Lokier wrote:
> Alan Cox wrote:
> > > Alan, can you send me again the list of CPUs you think
> > > is worth using 486 string routines.
> > > Sorry, i lost your previous mail.
> >
> > I suspect it is
> >
> > 486
> > K5
> > IDT Winchip
> > Rise
> > NexGen
> Take a look at

Nice page, thank you.

> Speed increases by 50% for unrolled string copies on their P5s. Sure
> they're old, but so are 486s :-)
> Of course you do _not_ want to inline a long string copy routine.
> There should probably be a arch/i386/lib/string-486.c.

These routines are often used and one of the goals was reducing code
size. That's why for generic case i used as few instructions as
while for optimized one i made some speedups with the cost of few
instructions more.

I don't see the point of string-486.c - string-486.h is a replacement
of string.h for i[45]86 machines so let stay in include directory.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.095 / U:1.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site