From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
Jiri Benc <jbenc@redhat.com>,
therbert@google.com, David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Routing loops & TTL tracking with tunnel devices
Date: Mon, 16 Nov 2015 14:28:52 -0800 [thread overview]
Message-ID: <1447712932.22599.77.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAHmME9pNCqbcoqbOnx6p8poehAntyyy1jQhy=0_HjkJ8nvMQdw@mail.gmail.com>
On Mon, 2015-11-16 at 21:55 +0100, Jason A. Donenfeld wrote:
> Hi Sowmini,
>
> Neat. Though, in my case, I'm not actually just prepending a header.
> I'm doing some more substantial transformations of a packet. And this
> needs to work with v4 too. So I'm not sure implementing a v6 spec will
> help with things. I need to identify the right mechanism inside the
> kernel to assist with this, like, say, a member in sk_buff.
There is very little chance we'll accept a new member in sk_buff, unless
proven needed.
Yes, it is very tempting and dozen of programmers already tried.
You'll have to demonstrate full understanding of the stack and why other
solutions do not work.
next prev parent reply other threads:[~2015-11-16 22:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 20:14 Jason A. Donenfeld
2015-11-16 20:37 ` Sowmini Varadhan
2015-11-16 20:55 ` Jason A. Donenfeld
2015-11-16 20:59 ` Sowmini Varadhan
2015-11-16 22:28 ` Eric Dumazet [this message]
2015-11-17 2:41 ` Jason A. Donenfeld
2022-04-29 0:37 ` Jason A. Donenfeld
2022-04-29 20:54 ` Eric Dumazet
2022-04-29 21:07 ` Jason A. Donenfeld
[not found] ` <d9854c74-c209-9ea5-6c76-8390e867521b@gmail.com>
2022-04-29 21:53 ` Jason A. Donenfeld
2022-04-29 22:05 ` Eric Dumazet
2022-04-29 22:09 ` Jason A. Donenfeld
2022-04-29 22:46 ` Eric Dumazet
2015-11-16 22:25 ` Hannes Frederic Sowa
2015-11-17 2:57 ` Jason A. Donenfeld
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=1447712932.22599.77.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.com \
--cc=therbert@google.com \
/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
all inboxes | Powered by JetHome®