From: Roberto Nibali <ratz@tac.ch>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Netfilter Developers <netfilter-devel@lists.netfilter.org>,
Pablo Neira <pablo@eurodev.net>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] update raw patch in POM [2.4.x]
Date: Wed, 22 Jun 2005 11:10:34 +0200 [thread overview]
Message-ID: <42B92B0A.2000802@tac.ch> (raw)
In-Reply-To: <Pine.LNX.4.58.0506220859360.5627@blackhole.kfki.hu>
Hello Jozsef,
I'm not running a 2.6.x kernel for the reasons explained below:
> Are you running a recent kernel from the 2.6 tree? A lot of improvements
> had been submitted in in spring and since then I have practically not
> received any reports on window tracking problems.
I know, however it's completely impossible for us to run 2.6.x kernels, too many
subtle changes are happening between new releases (ACPI routing, interrupt
mitigation in e1000, NAPI, and other subsystems besides networking) and some
features, like for example ipsec have changed fundamentally in the way they work
with regard to filtering or packet traversal. We unfortunately don't have enough
people to track and verify those changes regarding QA.
<off-topic>
A differnet point of view: I don't have the time nor do I get the money to
change our firewall software to be compatible with 2.6.x kernels. Also some
people's quest in trying to optimize latency (see RT threads on LKML) and tuning
mm/* for smoother desktop performance has a negative tendancy on network server
performance.
</off-topic>
Where would I best start to find out about differences between the 2.4.x and
2.6.x version of the tcp window tracking code? Do you remember when you stopped
backporting fixes?
Thanks for your interest,
Roberto Nibali, ratz
--
-------------------------------------------------------------
addr://Rathausgasse 31, CH-5001 Aarau tel://++41 62 823 9355
http://www.terreactive.com fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG Wir sichern Ihren Erfolg
-------------------------------------------------------------
next prev parent reply other threads:[~2005-06-22 9:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 11:06 [PATCH] update raw patch in POM Roberto Nibali
2005-06-07 14:37 ` Roberto Nibali
2005-06-07 22:55 ` Pablo Neira
2005-06-08 8:23 ` Roberto Nibali
2005-06-08 12:37 ` Pablo Neira
2005-06-14 15:27 ` Roberto Nibali
2005-06-20 8:18 ` Roberto Nibali
2005-06-20 9:07 ` Roberto Nibali
2005-06-20 10:41 ` SOLVED (was: Re: [PATCH] update raw patch in POM) Roberto Nibali
2005-06-20 11:01 ` Jozsef Kadlecsik
2005-06-20 11:03 ` SOLVED Roberto Nibali
2005-06-20 11:04 ` SOLVED Jozsef Kadlecsik
2005-06-20 10:49 ` [PATCH] update raw patch in POM Jan Engelhardt
2005-06-20 11:03 ` Roberto Nibali
2005-06-21 0:34 ` Thomas Graf
2005-06-21 0:39 ` Thomas Graf
2005-06-21 6:46 ` Roberto Nibali
2005-06-21 8:59 ` Pablo Neira
2005-06-21 9:08 ` Jozsef Kadlecsik
2005-06-21 11:18 ` Thomas Graf
2005-06-21 0:51 ` Pablo Neira
2005-06-21 11:13 ` Thomas Graf
2005-06-21 14:00 ` Patrick McHardy
2005-06-21 14:17 ` [PATCH] update raw patch in POM [2.4.x] Roberto Nibali
2005-06-21 14:47 ` Patrick McHardy
2005-06-21 15:15 ` Roberto Nibali
2005-06-21 15:32 ` Patrick McHardy
2005-06-22 9:26 ` Roberto Nibali
2005-06-22 7:04 ` Jozsef Kadlecsik
2005-06-22 9:10 ` Roberto Nibali [this message]
2005-06-22 9:19 ` Jozsef Kadlecsik
2005-06-22 9:27 ` Roberto Nibali
2005-06-21 21:50 ` [PATCH] update raw patch in POM Thomas Graf
2005-06-22 0:32 ` Patrick McHardy
2005-06-22 0:52 ` Thomas Graf
2005-06-22 3:24 ` Pablo Neira
2005-06-22 3:55 ` Patrick McHardy
2005-06-22 5:48 ` Roberto Nibali
2005-06-22 11:39 ` Roberto Nibali
2005-06-22 18:38 ` Patrick McHardy
2005-06-27 6:36 ` Roberto Nibali
2005-06-27 10:57 ` Patrick McHardy
2005-06-27 12:07 ` Roberto Nibali
2005-06-27 12:55 ` Patrick McHardy
2005-06-27 13:53 ` Roberto Nibali
2005-06-27 15:49 ` Patrick McHardy
2005-06-28 6:02 ` Roberto Nibali
2005-06-27 8:50 ` Roberto Nibali
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=42B92B0A.2000802@tac.ch \
--to=ratz@tac.ch \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.