Re: [PATCH 2/4] deferred drop, __parent workaround, reshape_fail
From: Harald Welte <hidden>
Date: 2004-08-16 07:20:32
Also in:
netfilter-devel
[removing lots of people from the Cc, since they are definitely on netdev and don't need to be Cc'ed at this state] Hi Jamal! On Fri, Aug 13, 2004 at 08:51:24AM -0400, jamal wrote:
Alessandro, This summary applies to all your patches: Too many changes that seem unnecessary. Take a deep breath.
I'm actually not as pessimistic about all his changes. Allesandro's ultimate goal seems to be connection-based accounting that accounts precisely which packets have actually hit the outgoing wire. While I'm quite happy with the now in-kernel conntrack accounting (basedo on Rx rather than Tx packets/bytes), this is a different definition of accounting. Let's discuss the individual patches seperately. 1) Is certainly not a huge issue, no debate here 2) I am not as familiar with the tc/scheduler code as you are, but I also think that what he is trying to achieve is a valid goal. He tries to make all tc-related packet drops go to a single code path for packet dropping. Independent of Allesandro's implementation, I would really like to see something like this. We once had an experimental patch called the 'dropped hook' that would be traversed for all packets dropped somewhere in the stack (for auditing in userspace, whatever). Having a single packet drop point makes such a change less intrusive. 3) Is already in davem's tree, no need for discusion ;) 4) This is the part you are complaining about, right? I agree, I don't like conntrack specific stuff in dev.c and packet scheduler areas.
cheers, jamal
-- - Harald Welte [off-list ref] http://www.netfilter.org/ ============================================================================ "Fragmentation is like classful addressing -- an interesting early architectural error that shows how much experimentation was going on while IP was being designed." -- Paul Vixie
Attachments
- signature.asc [application/pgp-signature] 189 bytes