DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] Xen DOM0 runtime support
Date: Mon, 26 Oct 2015 07:24:40 +0000	[thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC22BC3187@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1445582090-5927-1-git-send-email-stephen@networkplumber.org>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen
> Hemminger
> Sent: Friday, October 23, 2015 2:35 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 0/6] Xen DOM0 runtime support
> 
> It should be possible to build a single application or library that will work both
> in Xen and non-Xen environment. Any special case handling should be done
> at runtime.
> 
> Rebased to current DPDK source.
> 
> Stephen Hemminger (6):
>   xen: allow determining DOM0 at runtime
>   ethdev: add common function for reserving DMA regions
>   e1000: use rte_eth_dma_zone_reserve
>   ixgbe: use rte_eth_dma_zone_reserve
>   i40e: use rte_eth_dma_zone_reserve
>   fm10k: use rte_eth_dma_zone_reserve
> 
>  drivers/net/e1000/em_rxtx.c                  | 38 ++---------
>  drivers/net/e1000/igb_rxtx.c                 | 41 ++----------
>  drivers/net/fm10k/fm10k_ethdev.c             | 47 ++------------
>  drivers/net/i40e/i40e_ethdev.c               |  9 ---
>  drivers/net/i40e/i40e_fdir.c                 |  5 +-
>  drivers/net/i40e/i40e_rxtx.c                 | 94 ++++++----------------------
>  drivers/net/ixgbe/ixgbe_rxtx.c               | 47 ++------------
>  lib/librte_eal/common/include/rte_memory.h   | 30 ++++++++-
>  lib/librte_eal/linuxapp/eal/eal_memory.c     |  7 +++
>  lib/librte_eal/linuxapp/eal/eal_xen_memory.c |  2 +-
>  lib/librte_ether/rte_ethdev.c                | 24 +++++++
>  lib/librte_ether/rte_ethdev.h                | 23 +++++++
>  lib/librte_mempool/rte_mempool.c             | 48 +++++++++-----
>  lib/librte_mempool/rte_mempool.h             |  3 +-
>  14 files changed, 160 insertions(+), 258 deletions(-)
> 
> --
> 2.1.4

Acked-by: Jijiang Liu <Jijiang.liu@intel.com>

Thanks
Jijiang Liu

  parent reply	other threads:[~2015-10-26  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  6:34 Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 1/6] xen: allow determining DOM0 at runtime Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 2/6] ethdev: add common function for reserving DMA regions Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 3/6] e1000: use rte_eth_dma_zone_reserve Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 4/6] ixgbe: " Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 5/6] i40e: " Stephen Hemminger
2015-10-23  6:34 ` [dpdk-dev] [PATCH 6/6] fm10k: " Stephen Hemminger
2015-10-26  7:24 ` Liu, Jijiang [this message]
2015-11-03  0:40 ` [dpdk-dev] [PATCH v2 0/6] Xen DOM0 runtime support Thomas Monjalon

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=1ED644BD7E0A5F4091CF203DAFB8E4CC22BC3187@SHSMSX101.ccr.corp.intel.com \
    --to=jijiang.liu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).