From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 2/2]: Use `unsigned' for packet lengths
Date: Tue, 28 Nov 2006 20:04:51 +0000 [thread overview]
Message-ID: <200611282004.51657@strip-the-willow> (raw)
In-Reply-To: <200611281435.05466@strip-the-willow>
Quoting Ian McDonald:
| I think I didn't explain my point well here. You can't change to u32
| but need to be unsigned int (not u64).
Don't get this: u32 is a 32-bit unsigned value and therefore looks sufficient - and you
are proposing `unsigned int' to have easier conversion to skb->len, right?
| u32 is plenty but skb->len gets
| passed into the length parameter... Or that's how I read it anyway.
|
| e.g. net/dccp/output.c dccp_write_xmit:
| err = ccid_hc_tx_send_packet(dp->dccps_hc_tx_ccid, sk, skb,
| skb->len);
| which then goes through callback to the code in the patch.
OK, what do you suggest:
a) keep this callback interface, change `len' to `unsigned int'
b) keep this callback interface, patch as before (use u32)
c) change the callback interface, get rid of last argument (which is skb->len anyway)
and use `unsigned int' in ccid_hc_tx_packet_sent
???
| > I have two other suggestions regarding 64-bit unsigned - I think it would make sense to store
| > the calculated send rate in bytes per microsecond, since there are some nasty conversion problems
| > attached to it, as well as division errors. I am working on this right now.
| >
| Disagree if I understand you. This would imply minimum send rate of 1
| million bytes per second which is often not achievable.
No that is not what I meant. Of course this needs to be done with regard to proper conversion - in
particular, X_recv. I am at the moment trying to write this up (time consuming task), but the gist
of it is - we could eliminate some problems, such as (i) having to multiply by 1E12 when computing
X_calc, (ii) get better results when performing direct division. As said, will send further information.
Would really appreciate if you could at some time have a look at the moving-average patch. Have communicated
with Eddie again about it, and using MSS would at the moment be much more complicated.
next prev parent reply other threads:[~2006-11-28 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 14:35 [PATCH 2/2]: Use `unsigned' for packet lengths Gerrit Renker
2006-11-28 19:34 ` Ian McDonald
2006-11-28 19:41 ` Gerrit Renker
2006-11-28 19:49 ` Ian McDonald
2006-11-28 20:04 ` Gerrit Renker [this message]
2006-11-28 20:17 ` Ian McDonald
2006-11-28 20:27 ` Arnaldo Carvalho de Melo
2006-11-28 20:31 ` Gerrit Renker
2006-11-28 20:37 ` Arnaldo Carvalho de Melo
2006-11-28 20:53 ` Gerrit Renker
2006-11-28 21:01 ` Ian McDonald
2006-11-28 21:19 ` Eddie Kohler
2006-11-28 21:56 ` Gerrit Renker
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=200611282004.51657@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