From: Matthew Hall <mhall@mhcomputing.net>
To: daniel chapiesky <dchapiesky2@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_mbuf: documentation, meta-data, and inconsistencies
Date: Thu, 28 Aug 2014 20:09:16 -0700 [thread overview]
Message-ID: <20140829030916.GA26231@mhcomputing.net> (raw)
In-Reply-To: <CAJnwcoPgydbE9BOZCkMejcd4BpLpw7E3gtYnrdCWs0744qJTkg@mail.gmail.com>
On Thu, Aug 28, 2014 at 08:00:59PM -0400, daniel chapiesky wrote:
> But, in the end, sharing the meta-data area with the packet headroom seems
> to be a very
> bad idea.
>
> Sincerely,
>
> Daniel Chapiesky
You might have picked a good time to inquire about it as some of the Intel
guys are making patches to clean up rte_mbuf during the last couple of weeks
as we speak.
Matthew.
next prev parent reply other threads:[~2014-08-29 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 0:00 daniel chapiesky
2014-08-29 3:09 ` Matthew Hall [this message]
2014-08-29 23:22 ` [dpdk-dev] rte_memzone: memzone_reserve_aligned_thread_unsafe failed when running two process at the same time zimeiw
2014-08-30 14:22 ` Zhang, Jerry
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=20140829030916.GA26231@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dchapiesky2@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).