From: Eduard Gibert <edugibert@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mbuf: clarify comment on adding TX offload flags
Date: Thu, 9 Jul 2015 09:46:24 -0400 [thread overview]
Message-ID: <CABJjCfpTTUfkASLbAydY3yQpALxmt2AyCOofrh9pP+jT6jgH6g@mail.gmail.com> (raw)
In-Reply-To: <1436448159-8394-1-git-send-email-bruce.richardson@intel.com>
Hello,
I am trying to run any DPDK application in my machine but I'm unable to do
so because it always hangs after the print "EAL: Setting up memory.." That
applies to all of the DPDK applications. Anyone has any ideas on why this
is happening?
Thanks,
Eduard Gibert Renart
2015-07-09 9:22 GMT-04:00 Bruce Richardson <bruce.richardson@intel.com>:
> The comment for TX offload flags stated that those flags started at bit
> 55 and then were added to the right of that, leaving 8 bits reserved for
> generic mbuf (i.e. non-offload) use. This comment may not have been
> clear as 5 of the 8 flags which were reserved have now been used for TX
> offloads.
> This patch:
> * updates the description so that it now reflects reality that
> only three flags are available for generic mbuf use
> * reserved the final generic flag so that it can't be taken over for TX
> offload in future
> * clarifies the comment for TX flags to indicate that they should be
> counting downwards not upwards.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> lib/librte_mbuf/rte_mbuf.h | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
> index 80419df..0c0034b 100644
> --- a/lib/librte_mbuf/rte_mbuf.h
> +++ b/lib/librte_mbuf/rte_mbuf.h
> @@ -75,9 +75,10 @@ extern "C" {
> *
> * - RX flags start at bit position zero, and get added to the left of
> previous
> * flags.
> - * - The most-significant 8 bits are reserved for generic mbuf flags
> - * - TX flags therefore start at bit position 55 (i.e. 63-8), and new
> flags get
> - * added to the right of the previously defined flags
> + * - The most-significant 3 bits are reserved for generic mbuf flags
> + * - TX flags therefore start at bit position 60 (i.e. 63-3), and new
> flags get
> + * added to the right of the previously defined flags i.e. they should
> count
> + * downwards, not upwards.
> *
> * Keep these flags synchronized with rte_get_rx_ol_flag_name() and
> * rte_get_tx_ol_flag_name().
> @@ -197,6 +198,8 @@ extern "C" {
> */
> #define PKT_TX_OUTER_IPV6 (1ULL << 60)
>
> +#define __RESERVED (1ULL << 61) /**< reserved for future mbuf
> use */
> +
> #define IND_ATTACHED_MBUF (1ULL << 62) /**< Indirect attached mbuf */
>
> /* Use final bit of flags to indicate a control mbuf */
> --
> 2.4.3
>
>
next prev parent reply other threads:[~2015-07-09 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 13:22 Bruce Richardson
2015-07-09 13:46 ` Eduard Gibert [this message]
2015-07-09 13:59 ` Thomas Monjalon
2015-07-15 10:16 ` Olivier MATZ
2015-07-16 12:16 ` 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=CABJjCfpTTUfkASLbAydY3yQpALxmt2AyCOofrh9pP+jT6jgH6g@mail.gmail.com \
--to=edugibert@gmail.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).