Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Josh Litherland <josh@emperorlinux.com>
To: linux-raid@vger.kernel.org
Cc: research@emperorlinux.com
Subject: [PATCH] Simplify XOR template selection
Date: Sun, 20 Jun 2004 14:47:31 -0400	[thread overview]
Message-ID: <1087757251.12410.9.camel@JubJub> (raw)

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]


I found this output confusing:

raid5: measuring checksumming speed
   8regs     :  1896.000 MB/sec
   8regs_prefetch:  2396.000 MB/sec
   32regs    :  1772.000 MB/sec
   32regs_prefetch:  1664.000 MB/sec
   pIII_sse  :  2352.000 MB/sec
   pII_mmx   :  4696.000 MB/sec
   p5_mmx    :  6252.000 MB/sec
raid5: using function: pIII_sse (2352.000 MB/sec)

since it seemed to be choosing a sub-optimal function.  I read the code
and figured out why this is the way it is.  However, to save others the
same confusion I had, and maybe even save a few picoseconds on startup,
I humbly submit the attached patch.

-- 
Josh Litherland <josh@emperorlinux.com>
Emperor Linux

[-- Attachment #2: xor_selection.diff --]
[-- Type: text/x-patch, Size: 1719 bytes --]

diff -drauN linux-2.6.6/drivers/md/xor.c linux-2.6.6.new/drivers/md/xor.c
--- linux-2.6.6/drivers/md/xor.c	2004-05-09 22:32:37.000000000 -0400
+++ linux-2.6.6.new/drivers/md/xor.c	2004-06-20 14:26:21.000000000 -0400
@@ -108,29 +108,40 @@
 	}
 	b2 = b1 + 2*PAGE_SIZE + BENCH_SIZE;
 
-	printk(KERN_INFO "raid5: measuring checksumming speed\n");
+	/*
+	 * If this arch/cpu has a short-circuited selection, don't loop through all
+	 * the possible functions, just test the best one
+	 */
 
+	fastest = NULL;
+
+#ifdef XOR_SELECT_TEMPLATE
+		fastest = XOR_SELECT_TEMPLATE(fastest);
+#endif
+	
 #define xor_speed(templ)	do_xor_speed((templ), b1, b2)
 
-	XOR_TRY_TEMPLATES;
+	if (fastest) {
+		xor_speed(fastest);
+		printk("KERN_INFO raid5: automatically using best checksumming function: %s (%d.%03d MB/sec)\n",
+		       fastest->name, fastest->speed / 1000, fastest->speed % 1000);
+	} else {
+		printk(KERN_INFO "raid5: measuring checksumming speed\n");
+		XOR_TRY_TEMPLATES;
+		fastest = template_list;
+		for (f = fastest; f; f = f->next) 
+			if (f->speed > fastest->speed)
+				fastest = f;
+		printk("raid5: using function: %s (%d.%03d MB/sec)\n",
+		       fastest->name, fastest->speed / 1000, fastest->speed % 1000);
+
+	}
 
 #undef xor_speed
 
 	free_pages((unsigned long)b1, 2);
 
-	fastest = template_list;
-	for (f = fastest; f; f = f->next)
-		if (f->speed > fastest->speed)
-			fastest = f;
-
-#ifdef XOR_SELECT_TEMPLATE
-	fastest = XOR_SELECT_TEMPLATE(fastest);
-#endif
-
 	active_template = fastest;
-	printk("raid5: using function: %s (%d.%03d MB/sec)\n",
-	       fastest->name, fastest->speed / 1000, fastest->speed % 1000);
-
 	return 0;
 }
 

             reply	other threads:[~2004-06-20 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 18:47 Josh Litherland [this message]
2004-06-20 21:46 ` [PATCH] Simplify XOR template selection Josh Litherland

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=1087757251.12410.9.camel@JubJub \
    --to=josh@emperorlinux.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=research@emperorlinux.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