From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/4] qht-bench: document -p flag
Date: Wed, 28 Nov 2018 14:57:22 +0000 [thread overview]
Message-ID: <877egx45d9.fsf@linaro.org> (raw)
In-Reply-To: <20181123230206.12629-2-cota@braap.org>
Emilio G. Cota <cota@braap.org> writes:
> Which we forgot to do in bd224fce60 ("qht-bench: add -p flag
> to precompute hash values", 2018-09-26).
>
> Signed-off-by: Emilio G. Cota <cota@braap.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> tests/qht-bench.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/qht-bench.c b/tests/qht-bench.c
> index 2089e2bed1..636750d39f 100644
> --- a/tests/qht-bench.c
> +++ b/tests/qht-bench.c
> @@ -72,6 +72,7 @@ static const char commands_string[] =
> " -n = number of threads\n"
> "\n"
> " -o = offset at which keys start\n"
> + " -p = precompute hashes\n"
> "\n"
> " -g = set -s,-k,-K,-l,-r to the same value\n"
> " -s = initial size hint\n"
--
Alex Bennée
next prev parent reply other threads:[~2018-11-28 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 23:02 [Qemu-devel] [PATCH 0/4] xxhash patches for 4.0 Emilio G. Cota
2018-11-23 23:02 ` [Qemu-devel] [PATCH 1/4] qht-bench: document -p flag Emilio G. Cota
2018-11-28 14:57 ` Alex Bennée [this message]
2018-11-23 23:02 ` [Qemu-devel] [PATCH 2/4] exec: introduce qemu_xxhash{2,4,5,6,7} Emilio G. Cota
2018-11-23 23:02 ` [Qemu-devel] [PATCH 3/4] include: move exec/tb-hash-xx.h to qemu/xxhash.h Emilio G. Cota
2018-11-23 23:02 ` [Qemu-devel] [PATCH 4/4] xxhash: match output against the original xxhash32 Emilio G. Cota
2018-11-28 15:09 ` Alex Bennée
2018-12-14 0:45 ` [Qemu-devel] [PATCH 0/4] xxhash patches for 4.0 Richard Henderson
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=877egx45d9.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).