DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] Adjust mbuf flag definitions
Date: Fri,  3 Oct 2014 16:36:49 +0100	[thread overview]
Message-ID: <1412350612-23190-1-git-send-email-bruce.richardson@intel.com> (raw)

This patchset does some cleanup work on the mbuf flag definitions. It is 
based off the ideas discussed in the previous RFC patch. 
[Ref: http://thread.gmane.org/gmane.comp.networking.dpdk.devel/6155]

Summary of changes:
* Adjust TX flags to start at bit 55 in flags field and work downwards,
  leaving bits 56 upward reserved for generic mbuf flags, i.e. non-offload
  flags.
* Update the existing RX flags to be in a similar format to the newly
  redefined TX flags for clarity.
* Finally we add a comment for the ctrl mbuf flag to ensure all flags are
  properly documented.

Bruce Richardson (3):
  mbuf: move TX flags to group them near end of field
  mbuf: RX flag format update
  mbuf: add comment for ctrl mbuf flag

 lib/librte_mbuf/rte_mbuf.h | 65 +++++++++++++++++++++++++---------------------
 1 file changed, 36 insertions(+), 29 deletions(-)

-- 
1.9.3

             reply	other threads:[~2014-10-03 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 15:36 Bruce Richardson [this message]
2014-10-03 15:36 ` [dpdk-dev] [PATCH 1/3] mbuf: move TX flags to group them near end of field Bruce Richardson
2014-10-03 15:36 ` [dpdk-dev] [PATCH 2/3] mbuf: RX flag format update Bruce Richardson
2014-10-03 15:36 ` [dpdk-dev] [PATCH 3/3] mbuf: add comment for ctrl mbuf flag Bruce Richardson
2014-10-08 12:50 ` [dpdk-dev] [PATCH 0/3] Adjust mbuf flag definitions Thomas Monjalon

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=1412350612-23190-1-git-send-email-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.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).