From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/4]: Revamp TX hashing.
Date: Wed, 28 Jan 2009 12:41:26 -0800 (PST) [thread overview]
Message-ID: <20090128.124126.119524270.davem@davemloft.net> (raw)
In-Reply-To: <20090128090203.GA15674@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 28 Jan 2009 20:02:03 +1100
> One thing that I've been thinking about is that it would be
> really useful if we guaranteed that every inbound packet carried
> a hash with it. This could be used to help subsequent processing
> such as routing, netfilter, etc. since they all need to make
> decisions based on flows.
Ok, all the complicated cases will have to occur in decapsulators :-)
For example, IP tunnels would need to compute the hash as would most
forms of IPSEC since often we can't even see the inner flow until
after decryption even for transport cases.
prev parent reply other threads:[~2009-01-28 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 0:40 [PATCH 0/4]: Revamp TX hashing David Miller
2009-01-28 9:02 ` Herbert Xu
2009-01-28 20:41 ` David Miller [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=20090128.124126.119524270.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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).