netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@redhat.com>
Cc: shemminger@osdl.org, netdev@oss.sgi.com, devik@cdi.cz
Subject: Re: [PATCH 2.6]: Make packet scheduler clock source configurable
Date: Fri, 23 Jul 2004 01:36:22 +0200	[thread overview]
Message-ID: <41004F76.1080807@trash.net> (raw)
In-Reply-To: <20040721143110.4ab944bf.davem@redhat.com>

David S. Miller wrote:
> This looks great.
> 
> As you mention some platforms return zero, for example sparc32,
> for get_cycles().
> 
> I suggest we just expand the dependency list for NET_SCH_CLK_TSC
> to include SPARC64 PPC64 and perhaps some other easy to verify
> as having a working get_cycles() implementation.  I believe that
> as long as it increments at some rate >= jiffies, the psched
> calibration will get things into a working state.

It needs to increment at slightly above 1Mhz, otherwise delay will
be zero after this division and everything will fall apart:
delay /= rdelay.

> A lot of patches have been posted in this area and I'm losing
> track of what to apply first etc.  Can you repost your work
> one change at a time?  Thanks.

The following two patches remove some dead timer code and
change PSCHED_GET_TIME to use get_cycles. I'm going to send
the configurable clock-source patch tomorrow after checking
the arches.

Regards
Patrick

  reply	other threads:[~2004-07-22 23:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  2:21 [PATCH 2.6]: Make packet scheduler clock source configurable Patrick McHardy
2004-07-13  3:35 ` shemminger
2004-07-13  3:50   ` David S. Miller
     [not found]     ` <40F4862D.3070802@trash.net>
     [not found]       ` <40F4AC8B.40706@trash.net>
2004-07-21 21:31         ` David S. Miller
2004-07-22 23:36           ` Patrick McHardy [this message]
2004-07-23  0:17             ` David S. Miller
2004-07-23  0:52               ` Patrick McHardy
2004-07-23  1:00                 ` Patrick McHardy
2004-07-23  1:03                   ` David S. Miller
2004-07-23 17:14                 ` Patrick McHardy
2004-07-23 17:53                   ` Stephen Hemminger
2004-07-23 20:54                   ` David S. Miller
2004-07-23 23:18                     ` Patrick McHardy
2004-07-25  6:27                       ` David S. Miller
2004-07-25 21:56                         ` Patrick McHardy
2004-07-26  0:02                           ` David S. Miller
2004-07-23 20:57                   ` David S. Miller
2004-07-23 23:21                     ` Patrick McHardy
2004-07-13 16:16 ` Stephen Hemminger

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=41004F76.1080807@trash.net \
    --to=kaber@trash.net \
    --cc=davem@redhat.com \
    --cc=devik@cdi.cz \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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).