Date: Fri, 16 Dec 2005 14:42:05 +0000 From: Joao Barros <joao.barros@gmail.com> To: Scott Long <scottl@samsco.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/amr amr.c amr_cam.c amr_disk.c amr_pci.c amrio.h amrreg.h amrvar.h Message-ID: <70e8236f0512160642y3c41c62dkdaf66d3fe68ec55f@mail.gmail.com> In-Reply-To: <43A26D4A.9080403@samsco.org> References: <200512140326.jBE3QnUT010666@repoman.freebsd.org> <70e8236f0512151455g1231cb7oa74aa7d54cfd5b18@mail.gmail.com> <43A26D4A.9080403@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/16/05, Scott Long <scottl@samsco.org> wrote: > Joao Barros wrote: > > On 12/14/05, Scott Long <scottl@freebsd.org> wrote: > > > > > Any specific testing in mind or just stability? > > I'm a bit worried that old controllers (especially ones that predate the > move to i960 CPUs) might be broken with this. But yeah, stability > testing is always welcome. I'll put my MegaRAID Elite 1600 to the task :-) > It got beat up for about 2 weeks straight, > so I'm pretty confident that it's solid. Any plans to MFC this to 6.x? > Kris Kenneway spent a couple of weeks doing parallel tarball extractions > to an AMR array under 6.0+mega_amr.diff in order to characterize SMP > contention and thoroughput. For the sake of consistent benchmarking and testing (6.0 vs 6.0+diff, not 6.0 vs CURRENT) could you provide the patch? -- Joao Barros
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70e8236f0512160642y3c41c62dkdaf66d3fe68ec55f>