From: sandr8 <sandr8_NOSPAM_@crocetta.org>
To: hadi@cyberus.ca
Cc: Harald Welte <laforge@netfilter.org>,
devik@cdi.cz, netdev@oss.sgi.com,
netfilter-devel@lists.netfilter.org
Subject: Re: Billing 1: WAS (Re: [PATCH 2/4] deferred drop, __parent workaround, reshape_fail , netdev@oss.sgi.com ,
Date: Mon, 23 Aug 2004 11:33:19 +0200 [thread overview]
Message-ID: <4129B9DF.8030402@crocetta.org> (raw)
In-Reply-To: <1093187835.1042.95.camel@jzny.localdomain>
jamal wrote:
>Apologies for latency - was busy at (my real) work.
>
>
you don't have to apologize for that :) it's something
everybody can easily understand :)
>Let me break this email into several ones since it is getting long.
>
>On Tue, 2004-08-17 at 09:40, sandr8 wrote:
>
>
>>something like enqueue(dev) that will indirectly call dev->qdisc->enqueue
>>and handle in that single place that stuff that does not fit well in
>>net/core/dev.c
>>
>>
>
>Enqueue of _root_ qdisc is the place to do it.
>Maybe even dev.c calls to it. Lets defer this to the next email.
>
>
then i should add some code in every qdisc that can
be root and execute it only if it is actually root?
isn't it more complex?
>Let me say this:
>I am happy with Haralds billing patch which is already in as is.
>In other words, although there is an accounting discrepancy it is not
>that big.
>What does that mean? unbilling is not something to rush in and patch in
>if its going to have an impact on other pieces. It doesnt matter whether
>it goes in in 2.6.20 or doesnt even go in as far as i am concerned.
>However this shouldnt dicourage you because you have actually opened an
>issue we need to resolve. So please keep up the discussions.
>
>
sure, for the time being i thought to simply concentrate
on the rest and maintain it as indipendent as possible
from the choice that will be taken.
cheers
alessandro
next prev parent reply other threads:[~2004-08-23 9:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 0:48 [PATCH 2/4] deferred drop, __parent workaround, reshape_fail sandr8
2004-08-13 12:51 ` jamal
2004-08-13 14:09 ` sandr8
2004-08-14 21:21 ` jamal
2004-08-16 7:35 ` Harald Welte
2004-08-16 13:29 ` jamal
2004-08-24 18:57 ` Harald Welte
2004-08-25 12:12 ` jamal
2004-08-16 7:20 ` Harald Welte
2004-08-16 13:00 ` jamal
2004-08-16 13:08 ` Harald Welte
2004-08-16 15:19 ` sandr8
2004-08-17 11:52 ` jamal
2004-08-17 13:40 ` [PATCH 2/4] deferred drop, __parent workaround, reshape_fail , netdev@oss.sgi.com , sandr8
2004-08-22 15:17 ` Billing 1: WAS (Re: " jamal
2004-08-23 9:33 ` sandr8 [this message]
2004-08-24 18:38 ` Harald Welte
2004-08-22 15:38 ` Billing 2: WAS(Re: " jamal
2004-08-22 16:12 ` Billing 3: " jamal
2004-08-23 9:39 ` sandr8
2004-08-23 11:38 ` Billing 3-1: " jamal
2004-08-23 12:04 ` sandr8
2004-08-23 12:31 ` jamal
2004-08-23 11:58 ` Billing 3: " jamal
2004-08-23 12:27 ` sandr8
2004-08-25 11:34 ` jamal
2004-08-23 12:15 ` Billing 3-3: " jamal
2004-08-24 18:46 ` Billing 3: " Harald Welte
2004-08-25 11:50 ` jamal
2004-08-17 13:49 ` [PATCH 2/4] deferred drop, __parent workaround, reshape_fail sandr8
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=4129B9DF.8030402@crocetta.org \
--to=sandr8_nospam_@crocetta.org \
--cc=devik@cdi.cz \
--cc=hadi@cyberus.ca \
--cc=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.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).