From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH RFC 09/11] tcp: handle want_cookie clause via reqsk_put
Date: Tue, 28 Jul 2020 01:00:52 +0200 [thread overview]
Message-ID: <20200727230052.GN23458@breakpoint.cc> (raw)
In-Reply-To: 962243569496bee88d74b854549d853ca9a1a726.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> On Mon, 2020-07-27 at 11:00 +0200, Florian Westphal wrote:
> > Would need to duplicate timeout logic and so on which I wanted to
> > avoid.
>
> Yep that would be quite complex. I was wondering about something
> simpler, like using with LRU policy a static 4 slots circular buffer
> inside the msk (the one identified by the token). WDYT?
But where do I get the token to find the msk from the cookie ack?
Its not re-sent in the options afaics, unlike mp_capable case.
next reply other threads:[~2020-07-27 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 23:00 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-28 11:51 [MPTCP] Re: [PATCH RFC 09/11] tcp: handle want_cookie clause via reqsk_put Paolo Abeni
2020-07-27 10:23 Paolo Abeni
2020-07-27 9:00 Florian Westphal
2020-07-15 14:59 Paolo Abeni
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=20200727230052.GN23458@breakpoint.cc \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.