From: Michael Richardson <mcr@sandelman.ca>
To: Christian Hopps <chopps@chopps.org>
Cc: netdev@vger.kernel.org, chopps@labn.net, devel@linux-ipsec.org
Subject: Re: [devel-ipsec] xfrm/ipsec/iptfs and some new sysctls
Date: Sun, 21 Jul 2024 19:37:54 -0700 [thread overview]
Message-ID: <593029.1721615874@dyas> (raw)
In-Reply-To: <m2bk2rx2lb.fsf@dhcp-8377.meeting.ietf.org>
[-- Attachment #1.1: Type: text/plain, Size: 465 bytes --]
I think that:
xfrm_iptfs_reorder_window
and
xfrm_iptfs_drop_time
are parameters about receiving.
While
xfrm_iptfs_init_delay
and
xfrm_iptfs_max_qsize
are parameters about sender stuff.. I think the names should include that
indication. "xfrm_iptfs_sender_init_delay" maybe.
1M byte default for max_qsize feels big, it's 1000 x 1K packets.
I realize that isn't a lot at 10Gb/s+. I dunno.
How do you plan to get feedback on whether the defaults are working?
[-- Attachment #1.2: Signature --]
[-- Type: text/plain, Size: 242 bytes --]
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2024-07-22 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 19:27 xfrm/ipsec/iptfs and some new sysctls Christian Hopps
2024-07-22 2:37 ` Michael Richardson [this message]
2024-07-22 14:29 ` [devel-ipsec] " Christian Hopps
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=593029.1721615874@dyas \
--to=mcr@sandelman.ca \
--cc=chopps@chopps.org \
--cc=chopps@labn.net \
--cc=devel@linux-ipsec.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).