From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] mbuf: improve mbuf comments
Date: Wed, 05 Nov 2025 22:28:55 +0100 [thread overview]
Message-ID: <11692478.3WhfQktd6Z@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65530@smartserver.smartshare.dk>
05/11/2025 12:33, Morten Brørup:
> > From: Morten Brørup [mailto:mb@smartsharesystems.com]
> > Sent: Wednesday, 5 November 2025 12.28
> >
> > Updated the comment preceding the 'rearm_data' fields to reflect that
> > some
> > ethdev drivers don't really set the rearm_data fields on RX descriptor
> > rearm, but rather when pulling the packet from the descriptor.
> > By doing this, they avoid a store operation into the mbuf when they
> > rearm
> > the TX descriptor, and instead postpone it to later, where it will be
>
> Typo: TX descriptor -> RX descriptor.
Another Typo: RX -> Rx ;)
We agreed to prefer Tx/Rx capitalization in devtools/words-case.txt.
I personnaly think it is more correct, as it is not an acronym.
prev parent reply other threads:[~2025-11-05 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 11:28 Morten Brørup
2025-11-05 11:33 ` Morten Brørup
2025-11-05 21:28 ` Thomas Monjalon [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=11692478.3WhfQktd6Z@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).