netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	jussi.kivilinna@mbnet.fi, netdev@vger.kernel.org
Subject: Re: [PATCH v2 2/3] net_sched: Add accessor function for packet	length for qdiscs
Date: Wed, 30 Jul 2008 13:21:22 +0200	[thread overview]
Message-ID: <48904EB2.8060402@trash.net> (raw)
In-Reply-To: <20080730111915.GA6362@ff.dom.local>

Jarek Poplawski wrote:
> On Wed, Jul 30, 2008 at 12:47:31PM +0200, Patrick McHardy wrote:
>   
>> Jarek Poplawski wrote:
>>     
>>> On Sat, Jul 26, 2008 at 03:21:42PM +0200, Patrick McHardy wrote:
>>>       
> ...
>   
>>>> The other problem that affects all qdiscs supporting actions is
>>>> TC_ACT_QUEUED/TC_ACT_STOLEN getting mapped to NET_XMIT_SUCCESS
>>>> even though the packet is not queued, corrupting upper qdiscs'
>>>> qlen counters.
>>>>         
>>> Why can't we (temporarily) simply check such cl->un.leaf.q->q.qlen
>>> before and after enqueing?
>>>       
>> Thats really ugly, why not simply fix it correctly by
>> not lying to upper qdiscs?
>>     
>
> I thought it needs to wait for your audit. (Considering current
> state of NET_XMIT statuses it's simple and reliable.) Otherwise
> I'd prefer nice methods too.
>   
Well, the problems are already clear, someone just needs to fix them :)
I won't be able to do this until next week.



  reply	other threads:[~2008-07-30 11:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 23:34 [PATCH v2 0/3] Add size table feature for qdiscs Jussi Kivilinna
2008-07-19 23:35 ` [PATCH v2 1/3] net_sched: Add qdisc_enqueue wrapper Jussi Kivilinna
2008-07-19 23:35 ` [PATCH v2 2/3] net_sched: Add accessor function for packet length for qdiscs Jussi Kivilinna
2008-07-25 10:57   ` Jarek Poplawski
2008-07-25 10:57     ` David Miller
2008-07-25 11:37       ` Jarek Poplawski
2008-07-25 11:49         ` David Miller
2008-07-26 13:21           ` Patrick McHardy
2008-07-26 14:18             ` Jarek Poplawski
2008-07-30 10:47               ` Patrick McHardy
2008-07-30 11:19                 ` Jarek Poplawski
2008-07-30 11:21                   ` Patrick McHardy [this message]
2008-07-30 11:37                     ` Jarek Poplawski
2008-07-30 11:40                       ` Patrick McHardy
2008-07-30 11:48                         ` David Miller
2008-07-30 11:52                           ` Patrick McHardy
2008-07-30 12:19                             ` Jarek Poplawski
2008-07-30 20:50                             ` Jarek Poplawski
2008-07-25 11:53         ` Jarek Poplawski
2008-07-25 11:52           ` David Miller
2008-07-25 12:08             ` Jarek Poplawski
2008-07-25 12:16               ` David Miller
2008-07-25 12:29         ` Jussi Kivilinna
2008-07-25 12:54           ` Jarek Poplawski
2008-07-25 13:15             ` Jussi Kivilinna
2008-07-25 17:46               ` Jarek Poplawski
2008-07-25 18:02                 ` Jarek Poplawski
2008-07-19 23:35 ` [PATCH v2 3/3] net_sched: Add size table " Jussi Kivilinna
2008-07-20  7:09 ` [PATCH v2 0/3] Add size table feature " David Miller

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=48904EB2.8060402@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=jarkao2@gmail.com \
    --cc=jussi.kivilinna@mbnet.fi \
    --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).