From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: brian.haley@hp.com, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [RFC, PATCH] IPV6 : add 64 bits components in struct in6_addr to speedup ipv6_addr_equal() & ipv6_addr_any()
Date: Mon, 30 Apr 2007 12:22:57 -0700 (PDT) [thread overview]
Message-ID: <20070430.122257.68157976.davem@davemloft.net> (raw)
In-Reply-To: <46363EBD.1020102@cosmosbay.com>
From: Eric Dumazet <dada1@cosmosbay.com>
Date: Mon, 30 Apr 2007 21:08:45 +0200
> Maybe we could at least define a 'struct in6_addr_k' for internal
> structures only, to speedup some parts of IPV6 stack.
I think it's better to put this on the backburner for now :-)
We could achieve all of this if we start from the bottom
and work our way up.
Although there are many variations, the logic drivers use to use
skb_reserve() to align the receive header tends to take on a certain
pattern. We could pull that out into a common piece of code and then
make it ensure 64-bit alignment without a lot of pain.
The hard part of the work will be handling the cases that don't
fit the pattern, and don't forget about NET_IP_ALIGN :-)
next prev parent reply other threads:[~2007-04-30 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 14:28 [RFC, PATCH] IPV6 : add 64 bits components in struct in6_addr to speedup ipv6_addr_equal() & ipv6_addr_any() Eric Dumazet
2007-04-30 16:09 ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-30 16:27 ` Brian Haley
2007-04-30 18:59 ` David Miller
2007-04-30 19:08 ` Eric Dumazet
2007-04-30 19:22 ` David Miller [this message]
2007-04-30 19:10 ` David Miller
2007-04-30 21:34 ` Andi Kleen
2007-04-30 20:37 ` David 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=20070430.122257.68157976.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brian.haley@hp.com \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).