From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |WARNING| pw141487 [PATCH] doc/design: minor cleanus
Date: Sat, 22 Jun 2024 22:26:12 +0800 [thread overview]
Message-ID: <202406221426.45MEQC3O865756@localhost.localdomain> (raw)
In-Reply-To: <20240622145140.28803-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/141487
_apply patch failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sat, 22 Jun 2024 07:47:57 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
Apply patch set 141487 failed:
Checking patch doc/guides/contributing/design.rst...
error: while searching for:
Mbuf features
-------------
A designated area in mbuf stores "dynamically" registered fields and flags. It is the default choice for accommodating new features. The "dynamic" area consumes the remaining space in the mbuf, indicating that it's being efficiently utilized. However, the ``rte_mbuf`` structure must be kept small (128 bytes).
As more features are added, the space for existinG=g "static" fields (fields that are allocated statically) may need to be reconsidered and possibly converted to "dynamic" allocation. Adding a new static field or flag should be an exception. It must meet specific criteria including widespread usage, performance impact, and size considerations. Before adding a new static feature, it must be justified by its necessity and its impact on the system's efficiency.
Runtime Information - Logging, Tracing and Telemetry
error: patch failed: doc/guides/contributing/design.rst:63
error: doc/guides/contributing/design.rst: patch does not apply
next parent reply other threads:[~2024-06-22 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240622145140.28803-1-stephen@networkplumber.org>
2024-06-22 14:26 ` qemudev [this message]
2024-06-22 14:52 ` |SUCCESS| " checkpatch
2024-06-22 15:12 ` |WARNING| " dpdklab
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=202406221426.45MEQC3O865756@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=stephen@networkplumber.org \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).