From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 2/4] DCCP: Add more debugging
Date: Wed, 03 Jan 2007 11:40:20 +0000 [thread overview]
Message-ID: <200701031140.21022@strip-the-willow> (raw)
In-Reply-To: <200612281706.25874.ian.mcdonald@jandi.co.nz>
Hi Ian,
I have tested this at home and found a small error:
| + if (hctx->ccid3hctx_x != old_x) {
| + ccid3_pr_debug("X_prev=%llu, X_now=%llu, X_calc=%u, "
| + "X_recv=%llu\n", old_x, hctx->ccid3hctx_x,
| + hctx->ccid3hctx_x_calc, hctx->ccid3hctx_x_recv);
| ccid3_update_send_time(hctx);
=> old_x, x, and x_recv are all scaled by 2^6 and need to be divided (would give wrong results).
I have fixed this in the online version (3c_CCID3_add_more_debugging_McDonald.diff);
the inter-diff between previous and now is (having also updated `x' -> `X' for consistency):
diff -u b/net/dccp/ccids/ccid3.c b/net/dccp/ccids/ccid3.c
--- b/net/dccp/ccids/ccid3.c
+++ b/net/dccp/ccids/ccid3.c
@@ -100,8 +100,8 @@
hctx->ccid3hctx_delta = min_t(u32, hctx->ccid3hctx_t_ipi / 2,
TFRC_OPSYS_HALF_TIME_GRAN);
- ccid3_pr_debug("t_ipi=%u, delta=%u, s=%u, x=%llu\n",
- hctx->ccid3hctx_t_ipi, hctx->ccid3hctx_delta,
+ ccid3_pr_debug("t_ipi=%u, delta=%u, s=%u, X=%llu\n",
+ hctx->ccid3hctx_t_ipi, hctx->ccid3hctx_delta,
hctx->ccid3hctx_s, hctx->ccid3hctx_x >> 6);
}
@@ -148,8 +148,9 @@
if (hctx->ccid3hctx_x != old_x) {
ccid3_pr_debug("X_prev=%llu, X_now=%llu, X_calc=%u, "
- "X_recv=%llu\n", old_x, hctx->ccid3hctx_x,
- hctx->ccid3hctx_x_calc, hctx->ccid3hctx_x_recv);
+ "X_recv=%llu\n", old_x >> 6, hctx->ccid3hctx_x >> 6,
+ hctx->ccid3hctx_x_calc, hctx->ccid3hctx_x_recv >> 6);
+
ccid3_update_send_time(hctx);
}
}
next prev parent reply other threads:[~2007-01-03 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 4:06 [PATCH 2/4] DCCP: Add more debugging Ian McDonald
2007-01-03 11:40 ` Gerrit Renker [this message]
2007-01-03 21:52 ` Ian McDonald
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=200701031140.21022@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@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