From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kuba@kernel.org, hannes@stressinduktion.org, edumazet@google.com
Subject: Re: Routing loops & TTL tracking with tunnel devices
Date: Fri, 29 Apr 2022 23:07:47 +0200 [thread overview]
Message-ID: <YmxTo2hVwcwhdvjO@zx2c4.com> (raw)
In-Reply-To: <04f72c85-557f-d67c-c751-85be65cb015a@gmail.com>
Hi Eric,
On Fri, Apr 29, 2022 at 01:54:27PM -0700, Eric Dumazet wrote:
> > Anyway, it'd be nice if there were a free u8 somewhere in sk_buff that I
> > could use for tracking times through the stack. Other kernels have this
> > but afaict Linux still does not. I looked into trying to overload some
> > existing fields -- tstamp/skb_mstamp_ns or queue_mapping -- which I was
> > thinking might be totally unused on TX?
>
>
> if skbs are stored in some internal wireguard queue, can not you use
> skb->cb[],
>
> like many other layers do ?
This isn't for some internal wireguard queue. The packets get sent out
of udp_tunnel_xmit_skb(), so they leave wireguard's queues.
Jason
next prev parent reply other threads:[~2022-04-29 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 20:14 Routing loops & TTL tracking with tunnel devices 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
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 [this message]
[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=YmxTo2hVwcwhdvjO@zx2c4.com \
--to=jason@zx2c4.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).