From: pcaulfield@sourceware.org <pcaulfield@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/dlm/tests/usertest flood.c
Date: 27 Mar 2007 15:17:03 -0000 [thread overview]
Message-ID: <20070327151703.26516.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: pcaulfield at sourceware.org 2007-03-27 16:17:03
Modified files:
dlm/tests/usertest: flood.c
Log message:
Actually, MAX_INT is a bit of a bad idea under this new system.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/dlm/tests/usertest/flood.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
--- cluster/dlm/tests/usertest/flood.c 2007/03/27 15:02:42 1.3
+++ cluster/dlm/tests/usertest/flood.c 2007/03/27 15:17:03 1.4
@@ -34,7 +34,7 @@
fprintf(file, "\n");
fprintf(file, " -V Show version of %s\n", prog);
fprintf(file, " -h Show this help information\n");
- fprintf(file, " -m <num> Maximum number of locks to hold (default MAX_INT)\n");
+ fprintf(file, " -m <num> Maximum number of locks to hold (default 100000)\n");
fprintf(file, " -i <num> Show progress in <n> increments (default 1000)\n");
fprintf(file, " -n <num> Number of resources (default 10)\n");
fprintf(file, " -q Quit\n");
@@ -62,7 +62,7 @@
{
int flags = 0;
int lockops = 0;
- int maxlocks = INT_MAX;
+ int maxlocks = 100000;
int rescount = 10;
int increment = 1000;
int quiet = 0;
next reply other threads:[~2007-03-27 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 15:17 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-18 15:13 [Cluster-devel] cluster/dlm/tests/usertest flood.c pcaulfield
2007-03-27 15:02 pcaulfield
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=20070327151703.26516.qmail@sourceware.org \
--to=pcaulfield@sourceware.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).