From: "Huichao Cai" <chcchc88@163.com>
To: "Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com
Subject: Re:Re: [PATCH] ip_frag: add IPv4 fast fragment switch and test data
Date: Sat, 4 Jun 2022 10:19:38 +0800 (CST) [thread overview]
Message-ID: <6ac80b09.42b.1812c82cc0e.Coremail.chcchc88@163.com> (raw)
In-Reply-To: <a35a980e-61db-7e71-ded9-8b0b1ac08b92@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
I've seen some applications that have to rewrite fragment
functions themselves in order to use MBUF_FAST_FREE
features, such as iQiYi's DPVS.
[-- Attachment #2: Type: text/html, Size: 481 bytes --]
next prev parent reply other threads:[~2022-06-04 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:13 Huichao Cai
2022-06-03 23:50 ` Konstantin Ananyev
2022-06-04 2:13 ` Huichao Cai
2022-06-04 2:19 ` Huichao Cai [this message]
2022-06-04 11:36 ` Konstantin Ananyev
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=6ac80b09.42b.1812c82cc0e.Coremail.chcchc88@163.com \
--to=chcchc88@163.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
/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).