From: lijuan.tu@intel.com
To: dts@dpdk.org,Yaqi Tang <yaqi.tang@intel.com>
Cc: Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V5 3/3] tests/ice_buffer_split: ice PF enable buffer split
Date: 25 Dec 2022 21:09:49 -0800 [thread overview]
Message-ID: <e661bc$hup6a6@orsmga003-auth.jf.intel.com> (raw)
In-Reply-To: <20221220060953.160820-4-yaqi.tang@intel.com>
On Tue, 20 Dec 2022 06:09:53 +0000, Yaqi Tang <yaqi.tang@intel.com> wrote:
> Packets received in ice scalar path can be devided into two mempools with expected hdr and payload length/content specified by protocol type.
>
> Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
Acked-by: Lijuan Tu <lijuan.tu@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-12-26 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 6:09 [PATCH V5 0/3] " Yaqi Tang
2022-12-20 6:09 ` [dts][PATCH V5 1/3] test_plans/index: add new test plan for ice_buffer_split Yaqi Tang
2022-12-20 6:09 ` [dts][PATCH V5 2/3] test_plans/ice_buffer_split: ice PF enable buffer split Yaqi Tang
2022-12-20 6:09 ` [dts][PATCH V5 3/3] tests/ice_buffer_split: " Yaqi Tang
2022-12-20 9:33 ` Jiang, YuX
2022-12-21 6:38 ` Peng, Yuan
2022-12-26 5:09 ` lijuan.tu [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='e661bc$hup6a6@orsmga003-auth.jf.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yaqi.tang@intel.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 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).