From: Edward Cree <ecree@solarflare.com>
To: Alexander Petrovsky <askjuise@gmail.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: IP fragmentation
Date: Tue, 21 Jul 2020 13:33:45 +0100 [thread overview]
Message-ID: <8b809ac6-9e12-527c-d39e-0bab9dc743e2@solarflare.com> (raw)
In-Reply-To: <CAH57y_T9_K0L_cGjBQ+2C9UuRtw28Nqjk1FUB+F+3=WJVVZaqg@mail.gmail.com>
On 20/07/2020 15:47, Alexander Petrovsky wrote:
> Unfortunately, for UDP I can't pick some _random_ host in case the
> first _seen_ fragment it's not a First Fragment (frag_off=0, MF=1). In
> this case, I have to accumulate ALL fragments in map. And on each
> received fragment check, is all fragments are collected. I did it in
> my PoC with AF_XDP, but in PoC all seems unreliable.
That's why I say punt in that case (XDP_PASS and then have something
else downstream of it to handle the slowpath. However people did LB
before XDP came along. Idk, netfilter? Does that have hooks post-
reassembly?)
And probably when punting also record a map entry saying "we punted
this IPID" so that when the First Frag shows up, the slowpath gets
to see that one too and can do its reassembly.
So the map doesn't have to accumulate the fragments (the slowpath does
that), just their offsets and lengths so XDP can tell when all frags
have been passed to the slowpath and delete the map entry.
-ed
prev parent reply other threads:[~2020-07-21 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 8:15 IP fragmentation Alexander Petrovsky
2020-07-20 12:17 ` Edward Cree
2020-07-20 14:47 ` Alexander Petrovsky
2020-07-21 12:33 ` Edward Cree [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=8b809ac6-9e12-527c-d39e-0bab9dc743e2@solarflare.com \
--to=ecree@solarflare.com \
--cc=askjuise@gmail.com \
--cc=xdp-newbies@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 read-only IMAP folder(s) and NNTP newsgroup(s).