DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: konstantin.ananyev@intel.com
Cc: dev@dpdk.org, xuelin.shi@freescale.com
Subject: Re: [dpdk-dev] [PATCH v4] enforce rules of the cpu and ixgbe exchange data.
Date: Mon, 27 Jul 2015 16:18:25 +0200	[thread overview]
Message-ID: <2152064.QkQ5mbgbrx@xps13> (raw)
In-Reply-To: <1437029134-25191-1-git-send-email-xuelin.shi@freescale.com>

A quick review of this long pending patch would be great.
Thanks

2015-07-16 14:45, xuelin.shi@freescale.com:
> From: Xuelin Shi <xuelin.shi@freescale.com>
> 
> 1. cpu use data owned by ixgbe must use rte_le_to_cpu_xx(...)
> 2. cpu fill data to ixgbe must use rte_cpu_to_le_xx(...)
> 3. checking pci status with converted constant.
> 
> Signed-off-by: Xuelin Shi <xuelin.shi@freescale.com>

  reply	other threads:[~2015-07-27 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  6:45 xuelin.shi
2015-07-27 14:18 ` Thomas Monjalon [this message]
2015-07-27 14:43   ` Ananyev, Konstantin
2015-07-29  7:44     ` Xuelin Shi

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=2152064.QkQ5mbgbrx@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=xuelin.shi@freescale.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).