From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Patrick McHardy <kaber@trash.net>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution for packet schedulers
Date: Mon, 5 Mar 2007 11:09:28 -0800 [thread overview]
Message-ID: <20070305110928.25ce596c@freekitty> (raw)
In-Reply-To: <45EC5682.6000406@trash.net>
On Mon, 05 Mar 2007 18:42:26 +0100
Patrick McHardy <kaber@trash.net> wrote:
> David Miller wrote:
> > Frankly, I think now that we have ktime and all of the proper generic
> > infrastructure to do this stuff properly, I think we should just use
> > ktime for the packet scheduler across the board and just delete all of
> > that old by-hand timekeeping selection crap from pkt_sched.h
>
> Sounds good, I'm going to remove all other clock sources.
> Will resend in a couple of days after fixing a few more
> problems I noticed.
>
Don't bother changing netem. I have a version that uses hrtimer's
and doesn't use PSCHED() clock source anymore.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-03-05 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 19:05 [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution for packet schedulers Patrick McHardy
2007-03-04 19:05 ` [RFC TIME 01/03]: Add jiffies_to_nsecs/nsecs_to_jiffies Patrick McHardy
2007-03-04 19:05 ` [RFC NET_SCHED 02/03]: Replace gettimeofday clocksource by ktime Patrick McHardy
2007-03-04 19:05 ` [RFC NET_SCHED 03/03]: Add support for nano-second clock resolution Patrick McHardy
2007-03-05 0:25 ` [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution for packet schedulers David Miller
2007-03-05 17:42 ` Patrick McHardy
2007-03-05 19:09 ` Stephen Hemminger [this message]
2007-03-05 19:27 ` Patrick McHardy
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=20070305110928.25ce596c@freekitty \
--to=shemminger@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).