DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org, Jianbo Liu <jianbo.liu@linaro.org>
Cc: helin.zhang@intel.com, jingjing.wu@intel.com,
	jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH 0/5] i40e: vector poll-mode driver on ARM64
Date: Wed, 24 Aug 2016 12:49:52 +0200	[thread overview]
Message-ID: <21044268.noi9xJjxkq@xps13> (raw)
In-Reply-To: <1472032425-16136-1-git-send-email-jianbo.liu@linaro.org>

2016-08-24 15:23, Jianbo Liu:
> This patch set is to implement i40e vector PMD on ARM64.

Thanks for extending ARM support.

The current NIC support status is:
% git grep -l 'ARM.*=.*Y' doc/guides/nics/features/
doc/guides/nics/features/ixgbe.ini
doc/guides/nics/features/ixgbe_vec.ini
doc/guides/nics/features/ixgbe_vf.ini
doc/guides/nics/features/ixgbe_vf_vec.ini
doc/guides/nics/features/pcap.ini
doc/guides/nics/features/thunderx.ini
doc/guides/nics/features/virtio.ini
doc/guides/nics/features/virtio_vec.ini

To sum it up, only virtio, ixgbe (and specific thunderx device)
seems to be supported on ARM in DPDK 16.07.
Now you are bringing support of i40e on ARM.
Do you plan to support more devices in near future?
Who is interested to do and/or validate ARM support of other drivers?

  parent reply	other threads:[~2016-08-24 10:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  9:53 Jianbo Liu
2016-08-24  9:53 ` [dpdk-dev] [PATCH 1/5] i40e: extract non-x86 specific code from vector driver Jianbo Liu
2016-10-12  2:55   ` Zhang, Qi Z
2016-10-13  3:00     ` Jianbo Liu
2016-10-13 11:58       ` Zhang, Qi Z
2016-08-24  9:53 ` [dpdk-dev] [PATCH 2/5] i40e: implement vector PMD for ARM architecture Jianbo Liu
2016-08-26 14:20   ` Thomas Monjalon
2016-10-12  2:46   ` Zhang, Qi Z
2016-10-13  2:19     ` Jianbo Liu
2016-08-24  9:53 ` [dpdk-dev] [PATCH 3/5] i40e: enable i40e vector PMD on ARMv8a platform Jianbo Liu
2016-08-24  9:53 ` [dpdk-dev] [PATCH 4/5] i40e: make vector driver filenames consistent Jianbo Liu
2016-08-24  9:53 ` [dpdk-dev] [PATCH 5/5] maintainers: claim i40e vector PMD on ARM Jianbo Liu
2016-08-24 10:49 ` Thomas Monjalon [this message]
2016-08-24 13:30   ` [dpdk-dev] [PATCH 0/5] i40e: vector poll-mode driver on ARM64 Shreyansh Jain
2016-08-26  6:42   ` Jianbo Liu
2016-09-19 16:25 ` Bruce Richardson
2016-10-04  8:24   ` Thomas Monjalon
2016-10-14  3:59 ` [dpdk-dev] [PATCH v2 " Jianbo Liu
2016-10-14  4:00   ` [dpdk-dev] [PATCH v2 1/5] i40e: extract non-x86 specific code from vector driver Jianbo Liu
2016-10-14  4:00   ` [dpdk-dev] [PATCH v2 2/5] i40e: implement vector PMD for ARM architecture Jianbo Liu
2016-10-14 13:26     ` Jerin Jacob
2016-10-14  4:00   ` [dpdk-dev] [PATCH v2 3/5] i40e: enable i40e vector PMD on ARMv8a platform Jianbo Liu
2016-10-14 13:28     ` Jerin Jacob
2016-10-14  4:00   ` [dpdk-dev] [PATCH v2 4/5] i40e: make vector driver filenames consistent Jianbo Liu
2016-10-14  4:00   ` [dpdk-dev] [PATCH v2 5/5] maintainers: claim i40e vector PMD on ARM Jianbo Liu
2016-10-17 14:44   ` [dpdk-dev] [PATCH v2 0/5] i40e: vector poll-mode driver on ARM64 Bruce Richardson
2016-10-19  9:20     ` Bruce Richardson

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=21044268.noi9xJjxkq@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@linaro.org \
    --cc=jingjing.wu@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).