DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: update mbuf section of programmer's	guide for 1.8
Date: Thu, 18 Dec 2014 20:30:45 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C2049C8F7E@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1417537079-476-2-git-send-email-bruce.richardson@intel.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, December 2, 2014 4:18 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/2] doc: update mbuf section of programmer's guide for 1.8
> In Release 1.8, the mbuf structure was significantly reworked to add extra information, leading to the
> structure being split across two cache lines, and the data pointer being replaced by an offset. The
> description of the library in the programmer's guide document needs to be updated to take account of
> these changes.
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

 I have applied the patch to my tree next/dpdk-doc.

  reply	other threads:[~2014-12-18 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 16:17 [dpdk-dev] [PATCH 0/2] Update programmers guide doc, mbuf chapter Bruce Richardson
2014-12-02 16:17 ` [dpdk-dev] [PATCH 1/2] doc: update mbuf section of programmer's guide for 1.8 Bruce Richardson
2014-12-18 20:30   ` Iremonger, Bernard [this message]
2014-12-02 16:17 ` [dpdk-dev] [PATCH 2/2] doc: Updated image files for rte_mbuf changes in 1.8 Bruce Richardson
2014-12-12 11:21 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2014-12-18 21:02   ` Iremonger, Bernard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8CEF83825BEC744B83065625E567D7C2049C8F7E@IRSMSX108.ger.corp.intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \


* 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).