From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] e1000: fix the issue of wrongly reporting descriptor done
Date: Sun, 02 Aug 2015 23:55:10 +0200 [thread overview]
Message-ID: <1715977.YirRIvxXYr@xps13> (raw)
In-Reply-To: <1438223940-12582-1-git-send-email-wenzhuo.lu@intel.com>
2015-07-30 10:39, Wenzhuo Lu:
> Header buffer address for header split will be filled with the physical
> address for DMA, which is actually not needed at all, as header split
> hasn't been supported. Hardware requires the least bit of header address
> which is 'Descriptor Done' bit when write back should be set to 0 by driver.
> The issue is that if the user wants to reserve an odd number of bytes between
> the mbuf header and data buffer, the physical address to be filled in the
> descriptor would happen to be odd. That means the DD bit would be set to
> non-zero by driver. That will result in reporting descriptor done wrongly.
>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-08-02 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 2:39 [PATCH] e1000: fix the issue of wrongly reporting descriptor done Wenzhuo Lu
2015-08-02 21:55 ` 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=1715977.YirRIvxXYr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.