netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Ranko Zivojnovic <ranko@spidernet.net>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: [NET]: gen_estimator deadlock fix
Date: Fri, 13 Jul 2007 15:42:32 +0200	[thread overview]
Message-ID: <20070713134231.GC3282@ff.dom.local> (raw)
In-Reply-To: <1184329602.16732.16.camel@ranko-fc2.spidernet.net>

On Fri, Jul 13, 2007 at 03:26:42PM +0300, Ranko Zivojnovic wrote:
> On Fri, 2007-07-13 at 14:17 +0200, Jarek Poplawski wrote:
> > On Thu, Jul 12, 2007 at 08:48:45PM +0300, Ranko Zivojnovic wrote:
> > ...
> > > Ok - here's the patch for a review - it compiles clean ... and that's as
> > > much as it has been tested - I'll try give it a run later today or
> > > definitely tomorrow.
> > ...
> > 
> > Ranko, you have some powers!
> > 
> > Alas, I definitely need more time. I hope I'll manage to check this
> > till monday. Of course, if testing will be OK and somebody will check
> > and ack this earlier I don't see any reason in waiting on my opinion.
> 
> Don't bother - just tested and it is a no-go (it would have been a
> wander if it worked from the first time :)) - have to resolve the issues
> with qdiscs that do not calculate/use rates...
> 
> I'm not sure if it is desirable to have rates available on all qdiscs -
> even on pfifo_fast... that way, when you issue...
> 
> # tc -s qdisc show dev eth0
> qdisc pfifo_fast 0: root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
>  Sent 115971059 bytes 196761 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> 
> ...you will not get the 'rate 0bit'.
> 

I've been a bit tight on time today, and only now I see that maybe
you have done too much. Of course, you can do it your way, but I
think it should be easier not change too much at once, so if possible
only include structs bstats and rate_est into struct gen_estimator
and do otherwise in these few sch_'s and act_'s which use this plus
all acceses and allocs changed appropriately. So it should be only 6
or 7 files affected. It seems no changes about gen_stats are necessary
now (next patch?).

I really can't check more now (or answer until monday).

Bye,
Jarek P.

PS: I'm in a little hurry now so I hope I'm not very wrong above...

  reply	other threads:[~2007-07-13 13:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 13:41 [NET]: gen_estimator deadlock fix Ranko Zivojnovic
2007-07-12  7:37 ` Jarek Poplawski
2007-07-12  9:18   ` Ranko Zivojnovic
2007-07-12  9:40     ` Ranko Zivojnovic
2007-07-12 10:46     ` Jarek Poplawski
2007-07-12 11:47       ` Ranko Zivojnovic
2007-07-12 12:07         ` Patrick McHardy
2007-07-12 17:48           ` Ranko Zivojnovic
2007-07-13 12:17             ` Jarek Poplawski
2007-07-13 12:26               ` Ranko Zivojnovic
2007-07-13 13:42                 ` Jarek Poplawski [this message]
2007-07-16  7:00                   ` Jarek Poplawski
2007-07-16 13:03                     ` Patrick McHardy
2007-07-16 17:45                       ` Ranko Zivojnovic
2007-07-17  1:28                         ` David Miller
2007-07-17 12:04                         ` Jarek Poplawski
2007-07-17 12:01                           ` Patrick McHardy
2007-07-17 12:28                             ` Jarek Poplawski

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=20070713134231.GC3282@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=ranko@spidernet.net \
    /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).