From: Bruce Richardson <bruce.richardson@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] enic: fix misalignment of Rx mbuf data
Date: Wed, 4 May 2016 11:22:48 +0100 [thread overview]
Message-ID: <20160504102248.GA24996@bricha3-MOBL3> (raw)
In-Reply-To: <1461725516-7166-1-git-send-email-johndale@cisco.com>
On Tue, Apr 26, 2016 at 07:51:56PM -0700, John Daley wrote:
> Data DMA used m->data_off of uninitialized mbufs instead of
> RTE_PKTMBUF_HEADROOM, potentially causing Rx data to be
> placed at the wrong alignment in the mbuf.
>
> Fixes: 947d860c821f ("enic: improve Rx performance")
> Signed-off-by: John Daley <johndale@cisco.com>
> ---
> drivers/net/enic/enic_main.c | 5 +++--
> drivers/net/enic/enic_rx.c | 6 ++++--
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
Applied to dpdk-next-net/rel_16_07
/Bruce
prev parent reply other threads:[~2016-05-04 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 2:51 John Daley
2016-05-04 10:22 ` Bruce Richardson [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=20160504102248.GA24996@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.com \
/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).