Date: Fri, 4 May 2012 01:24:11 +0900 From: rozhuk.im@gmail.com To: "'Attilio Rao'" <attilio@freebsd.org>, "'Steven Atreju'" <snatreju@googlemail.com> Cc: current@freebsd.org, 'Luigi Rizzo' <rizzo@iet.unipi.it>, "'K. Macy'" <kmacy@freebsd.org>, net@freebsd.org Subject: RE: fast bcopy... Message-ID: <4fa2b135.c4600e0a.153f.03f9@mx.google.com> In-Reply-To: <CAJ-FndDFg3eGHfiGtPSHgc06dFPB7VUZAq1moZxZBy=6n_rNRA@mail.gmail.com> References: <20120502182557.GA93838@onelab2.iet.unipi.it> <20120502215249.GT633@sherwood.local> <CAHM0Q_NNoMrtwcz-xoQ34oVmgJSyjeb_7O6qBHCe16eFeTot_w@mail.gmail.com> <20120503102844.GU633@sherwood.local> <CAJ-FndDFg3eGHfiGtPSHgc06dFPB7VUZAq1moZxZBy=6n_rNRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > guess this is a good time to thank the FreeBSD hackers for that FPU > > stack FILD/FISTP idea! > > I'll append the copy related notes of our doc/memperf.txt. > > Thanks, >=20 > I made an implementation of fpu unwinding and mmx copy to see if they > were really making a difference years ago (reimplementing bcopy, > memcopy, etc.). Codecs, such as Ffdshow often contain their own functions to work with = memory.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4fa2b135.c4600e0a.153f.03f9>