From: Julien Lafaye <jlafaye@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Packet statistics accounting module: request for comments
Date: Wed, 5 Oct 2011 21:27:34 +0200 [thread overview]
Message-ID: <CAFAca_C06BCQsovvjW8wUzAo=hR2tceAiTyEjGyU1e2D+b-EFQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1110042220390.10811@frira.zrqbmnf.qr>
Jan
> I still think this could be integrated, perhaps as an extra option to
> choose a particular recording mode, to xt_quota2 (including the fifo).
> Speaking of which, your module seems to lack locking on the ctx, so it's
> not very consistent on SMP as of yet.
>
I will fix the usage of the fifo so that there is not any odd behavior
in SMP context.
As for the inclusion into xt_quota2, I am bit skeptical, for three reasons:
- the two modules, xt_quota2 and xt_pktstat, have different features:
quota enforcement and poll-based network accounting for the first one,
and event driven high resolution network accounting for the second
one. Where I agree that the two modules could share portions of code,
I don't see how the core parts can be merged. I fear that merging the
modules would require putting the two codes side by side and not
actually merging them. But you have more experience than me on
netfilter modules, and obviously on xt_quota2, and you could give me
some hints on how to merge them in a way that would benefit the two
projects.
- xt_quota2 is clearly not a good name for the feature I propose.
- since the features provided by xt_quota2 and xt_pktstat are
separated, why trying to join them into a swiss-army knife with two
sets of parameters: one to be used for a first feature and the other
one for a second feature. This could prove to be misleading for the
user.
What do you think ?
Regards,
Julien
prev parent reply other threads:[~2011-10-05 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 4:50 Packet statistics accounting module: request for comments Julien Lafaye
2011-10-04 11:02 ` Jan Engelhardt
2011-10-04 19:03 ` Julien Lafaye
2011-10-04 20:27 ` Jan Engelhardt
2011-10-05 19:27 ` Julien Lafaye [this message]
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='CAFAca_C06BCQsovvjW8wUzAo=hR2tceAiTyEjGyU1e2D+b-EFQ@mail.gmail.com' \
--to=jlafaye@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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).