From: Daniel Borkmann <dborkman@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, fengguang.wu@intel.com
Subject: [PATCH net-next 3/3] lib: crc32: reduce number of cases for crc32{,c}_combine
Date: Mon, 4 Nov 2013 17:10:27 +0100 [thread overview]
Message-ID: <c3a8d8671b3d9b7763e3fac7a70be877b8f8ebab.1383580331.git.dborkman@redhat.com> (raw)
In-Reply-To: <cover.1383580331.git.dborkman@redhat.com>
In-Reply-To: <cover.1383580331.git.dborkman@redhat.com>
We can safely reduce the number of test cases by a tenth.
There is no particular need to run as many as we're running
now for crc32{,c}_combine, that gives us still ~8000 tests
we're doing if people run kernels with crc selftests enabled
which is perfectly fine.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
---
lib/crc32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/crc32.c b/lib/crc32.c
index 3a1dfa8..70f00ca 100644
--- a/lib/crc32.c
+++ b/lib/crc32.c
@@ -1037,7 +1037,7 @@ static int __init crc32c_combine_test(void)
int i, j;
int errors = 0, runs = 0;
- for (i = 0; i < 100; i++) {
+ for (i = 0; i < 10; i++) {
u32 crc_full;
crc_full = __crc32c_le(test[i].crc, test_buf + test[i].start,
@@ -1131,7 +1131,7 @@ static int __init crc32_combine_test(void)
int i, j;
int errors = 0, runs = 0;
- for (i = 0; i < 100; i++) {
+ for (i = 0; i < 10; i++) {
u32 crc_full;
crc_full = crc32_le(test[i].crc, test_buf + test[i].start,
--
1.8.3.1
next prev parent reply other threads:[~2013-11-04 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 16:10 [PATCH net-next 0/3] crc/csum follow-ups Daniel Borkmann
2013-11-04 16:10 ` [PATCH net-next 1/3] net: checksum: fix warning in skb_checksum Daniel Borkmann
2013-11-04 16:10 ` [PATCH net-next 2/3] lib: crc32: conditionally resched when running testcases Daniel Borkmann
2013-11-04 16:10 ` Daniel Borkmann [this message]
2013-11-04 20:27 ` [PATCH net-next 0/3] crc/csum follow-ups David Miller
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=c3a8d8671b3d9b7763e3fac7a70be877b8f8ebab.1383580331.git.dborkman@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).