From: taozj888 <taozj888@163.com>
To: "David Marchand" <david.marchand@redhat.com>
Cc: dev@dpdk.org
Subject: Re:Re: [PATCH v2 0/3] example/l3fwd: relax l3fwd rx RSS/Offload if needed
Date: Sun, 15 Oct 2023 22:06:45 +0800 (CST) [thread overview]
Message-ID: <364fb8b8.1bad.18b33a92723.Coremail.taozj888@163.com> (raw)
In-Reply-To: <CAJFAV8xc_EN+Hj34kpJgekLe5Fa5c=JULWXVTJVv86s6jJd=3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
Hi David:
Thanks for your notifications. I will check them in the future work.
Trevor Tao
At 2023-10-13 15:07:03, "David Marchand" <david.marchand@redhat.com> wrote:
>Hello,
>
>On Fri, Oct 13, 2023 at 6:28 AM Trevor Tao <taozj888@163.com> wrote:
>>
>> This series tries to relax l3fwd rx RSS/Offload mode requirement if they
>> are not supported by underlying hw or virtual devices, there is an
>> option named relax_rx_mode added to enable this option.
>>
>> Trevor Tao (3):
>> examples/l3fwd: relax RSS requirement with option
>> examples/l3fwd: relax the Offload requirement
>> doc: add a relax rx mode requirement option
>>
>> doc/guides/rel_notes/release_23_11.rst | 251 +++++++++++++++++++++---
>> doc/guides/sample_app_ug/l3_forward.rst | 4 +-
>> examples/l3fwd/l3fwd.h | 12 +-
>> examples/l3fwd/l3fwd_em.h | 2 +-
>> examples/l3fwd/l3fwd_lpm.h | 2 +-
>> examples/l3fwd/main.c | 30 +++
>> 6 files changed, 272 insertions(+), 29 deletions(-)
>
>Thanks for the patches.
>One comment on the form though.
>
>I see 4 batches of "v2 patches" in patchwork.
>https://patchwork.dpdk.org/project/dpdk/list/?submitter=3044&state=*
>I marked all but the last batch as superseded.
>If there is something wrong with this, please register to patchwork
>with your mail address, you will then be able to update the states
>yourself.
>
>
>It is hard to follow what work has been done between those different
>iterations of patches.
>For future submissions, don't forget to version your patches with a
>new revision (iirc, we should be at version 7 if I count the initial
>standalone v1 patch).
>
>In the cover letter, please provide a changelog of the differences
>between revisions.
>If you think it is better, you may put a more detailed changelog in
>each patch commitlog (as annotations, after ---).
>
>
>Thanks.
>
>--
>David Marchand
[-- Attachment #2: Type: text/html, Size: 2516 bytes --]
prev parent reply other threads:[~2023-10-15 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 4:27 Trevor Tao
2023-10-13 4:27 ` [PATCH v2 1/3] examples/l3fwd: relax RSS requirement with option Trevor Tao
2023-10-17 18:06 ` Konstantin Ananyev
2023-10-13 4:27 ` [PATCH v2 2/3] examples/l3fwd: relax the Offload requirement Trevor Tao
2023-10-17 18:13 ` Konstantin Ananyev
2023-10-13 4:27 ` [PATCH v2 3/3] doc: add a relax rx mode requirement option Trevor Tao
2023-10-31 20:08 ` Stephen Hemminger
2023-10-13 7:07 ` [PATCH v2 0/3] example/l3fwd: relax l3fwd rx RSS/Offload if needed David Marchand
2023-10-15 14:06 ` taozj888 [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=364fb8b8.1bad.18b33a92723.Coremail.taozj888@163.com \
--to=taozj888@163.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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).