netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Cc: kaber@trash.net, kadlec@blackhole.kfki.hu,
	kisza@securityaudit.hu, netfilter-devel@lists.netfilter.org,
	usagi-core@linux-ipv6.org, netdev@oss.sgi.com,
	David Miller <davem@redhat.com>
Subject: Re: Do you know about skb_header_pointer() ?
Date: Thu, 19 Aug 2004 11:44:01 +0200	[thread overview]
Message-ID: <20040819094401.GY3921@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <200408190721.QAA02944@toshiba.co.jp>

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

[Cc'ing davem]

On Thu, Aug 19, 2004 at 04:21:19PM +0900, Yasuyuki Kozakai wrote:

> According to a message in "netdev" mailing list, skb_header_pointer() will be
> introduced in mainline kernel. (see attached message)

yes, David Miller did so.  

If I remember correctly, his reasoning for skb_header_pointer() was that
even though we are not guaranteed a completely linear transport layer
header, it doesn't really happen at any point in the network stack at
this time.

I personally still like Yasuyuki's implementation[1] better, especially as
long as I'm not convinced that even in the event of IPv6 extension
headers, tunnels, ipsec, whaetever we're can still assume that
everything up to (and including) tcp option headers is linear.

And I still owe Dave some profiles on whether skb_header_pointer() as
opoosed to skb_copy_bits() actually still shows up in the profiles or not.

I'll do this _right now_ before some customer starts to annoy me again
with some stupid problem ;)

> If I remember correctly, this approach was rejected in the result of our
> discussions. And I sent a patch to this mailing list at 2004/08/08.

Yes, I thought your approach is better ;)  But maybe I'm just
overgeneralizing or trying to be too perfect.  Anyway, in the end it's
Dave's call.

[1]
http://lists.netfilter.org/pipermail/netfilter-devel/2004-August/016277.html

-- 
- Harald Welte <laforge@netfilter.org>             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

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

       reply	other threads:[~2004-08-19  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200408190721.QAA02944@toshiba.co.jp>
2004-08-19  9:44 ` Harald Welte [this message]
2004-08-19 14:16   ` Do you know about skb_header_pointer() ? David S. Miller
2004-08-19 16:55     ` Harald Welte
2004-08-19 14:17   ` David S. Miller
2004-08-19 17:00     ` Harald Welte
2004-08-19 17:27       ` David S. Miller

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=20040819094401.GY3921@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=davem@redhat.com \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=kisza@securityaudit.hu \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=usagi-core@linux-ipv6.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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).