From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ixgbe: fix RX is not working properly when buffer address is not word aligned
Date: Mon, 03 Aug 2015 21:41:39 +0200 [thread overview]
Message-ID: <1654946.GBBfK7fVZs@xps13> (raw)
In-Reply-To: <1438624781-28184-1-git-send-email-konstantin.ananyev@intel.com>
2015-08-03 18:59, Konstantin Ananyev:
> Niantic HW expects Header Buffer Address in the RXD to be word aligned.
> So, if mbuf's buf_physaddr is not word aligned then
> RX path will not work properly.
> Right now, in ixgbe PMD we always setup Packet Buffer Address(PBA) and
> Header Buffer Address (HBA) to the same value:
> buf_physaddr + RTE_PKTMBUF_HEADROOM.
> As ixgbe PMD doesn't support split header feature anyway,
> the issue can be fixied just by always setting HBA in the RXD to zero.
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-08-03 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 17:59 Konstantin Ananyev
2015-08-03 19:41 ` 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=1654946.GBBfK7fVZs@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).