All of lore.kernel.org
 help / color / mirror / Atom feed
From: netfilter@interlinx.bc.ca
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: testing checksum in helpers is redundant with tcp_window_tracking
Date: Thu, 27 Feb 2003 17:21:55 -0500	[thread overview]
Message-ID: <20030227222154.GA9692@pc.ilinx> (raw)

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Would it not be a good idea to have some kind of macro defined when
tcp_window_tracking in built into netfilter so that all of the helpers
and other code that are doing things like TCP checksum verification
and whatnot, can avoid wasting cycles doing it a second time?

Then helpers could wrap their tcp checksum calls with something like:

#ifndef TCP_WINDOW_TRACKING
...
#endif

Or is a runtime check a better idea?  If so what test could be done at
runtime to know that tcp_window_tracking is checking TCP checksums?

b.

-- 
Brian J. Murrell

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-02-27 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 22:21 netfilter [this message]
2003-02-28  9:04 ` testing checksum in helpers is redundant with tcp_window_tracking Patrick Schaaf
2003-02-28 10:33 ` Jozsef Kadlecsik
2003-02-28 12:13   ` netfilter

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=20030227222154.GA9692@pc.ilinx \
    --to=netfilter@interlinx.bc.ca \
    --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 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.