From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 1/3]: Inline for time delta
Date: Sat, 16 Jun 2007 15:00:25 +0000 [thread overview]
Message-ID: <200706161600.25348@strip-the-willow> (raw)
In-Reply-To: <200706091932.15559@strip-the-willow>
Quoting Arnaldo Carvalho de Melo:
| > I am going to change that in my tree as well, since I am busy updating with regard
| > to most recent changes anyway.
|
| I just checked with Thomas Gleixner, the ktime_t guy and he is ok with
| adding ktime_us_delta() to ktime.h, which I have in my tree already.
Ok when that comes through, the patch can simply be dropped.
| I'm now staring at this:
| /* set the nominal send time for the next following packet */
| - timeval_add_usecs(&hctx->ccid3hctx_t_nom, hctx->ccid3hctx_t_ipi);
| + hctx->ccid3hctx_t_nom = ktime_add_ns(hctx->ccid3hctx_t_nom,
| + hctx->ccid3hctx_t_ipi * 1000);
|
| I'm thinking about just keeping t_ipi in nanoseconds to avoid doing
| the multiplies back and forth, but haven't fully looked at the other
| t_ipi uses, quick thoughts? Stupid idea?
Please keep it for the moment. The packet scheduler needs an overhaul in any case,
so the above IMO is the simplest way of aligning the old code with the new interface.
Overhauling the packet scheduler will cost some work, but it is one of the next items
that should be addressed when through with the current set of patches.
next prev parent reply other threads:[~2007-06-16 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 18:32 [PATCH 1/3]: Inline for time delta Gerrit Renker
2007-06-10 5:55 ` Ian McDonald
2007-06-11 8:18 ` Gerrit Renker
2007-06-11 8:34 ` Ian McDonald
2007-06-16 14:04 ` Arnaldo Carvalho de Melo
2007-06-16 14:44 ` Gerrit Renker
2007-06-16 14:55 ` Arnaldo Carvalho de Melo
2007-06-16 15:00 ` Gerrit Renker [this message]
2007-06-16 15:01 ` Arnaldo Carvalho de Melo
2007-06-16 15:12 ` Arnaldo Carvalho de Melo
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=200706161600.25348@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.