From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] Adjust mbuf flag definitions
Date: Wed, 08 Oct 2014 14:50:26 +0200 [thread overview]
Message-ID: <1467636.AzLFRR9WOp@xps13> (raw)
In-Reply-To: <1412350612-23190-1-git-send-email-bruce.richardson@intel.com>
2014-10-03 16:36, Bruce Richardson:
> 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
Acked and applied
Thanks
--
Thomas
prev parent reply other threads:[~2014-10-08 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 15:36 Bruce Richardson
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 ` 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=1467636.AzLFRR9WOp@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=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).