From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Yongseok Koh <yskoh@mellanox.com>,
nelio.laranjeiro@6wind.com, dev@dpdk.org,
Raslan Darawsheh <rasland@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Xueming Li <xuemingl@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1 0/7] net/mlx5: add vectorized Rx/Tx burst for ARM
Date: Mon, 9 Oct 2017 09:45:18 +0200 [thread overview]
Message-ID: <20171009074518.GE13551@6wind.com> (raw)
In-Reply-To: <51bda660-2653-1416-539d-1333e4f0da04@intel.com>
On Mon, Oct 09, 2017 at 03:39:47AM +0100, Ferruh Yigit wrote:
> On 10/6/2017 12:00 AM, Yongseok Koh wrote:
> > Add dataplane functions using ARM NEON instructions. To modularize vectorized
> > functions for different architectures, the existing files having x86 SSE support
> > is reorganized.
> >
> > This patchset has dependency with the following patches:
> > - net/mlx5: fix overflow of Rx SW ring
> > - Nelio's mlx5 flow cleanup patchset, the last one is:
> > [dpdk-dev,v2,30/30] net/mlx5: add new operations for isolated mode
>
> - Nelio's set was waiting Xueming's which is merged now.
> - Nelio's set will have v3 because of your comments.
> - And Raslan's patch is dependent on yours.
>
> So, if I don't miss anything
> - first there will be Nelio's v3
> - Later this patchset on top of it
> - Later Raslan's on top of yours
>
> With multiple developers working on same drivers, mlx drivers become
> hard to manage/trace.
>
> next-net-mlx sound like good idea :) Any comment on this?
Sounds good to me too, particularly so since we do have such a tree
internally where we constantly rebase series on top of one another for
non-regression testing purposes.
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2017-10-09 7:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 23:00 Yongseok Koh
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 1/7] net/mlx5: cleanup memory barriers Yongseok Koh
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 2/7] net/mlx5: rename a file of SSE Rx/Tx Yongseok Koh
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 3/7] net/mlx5: use static assert for compile-time sanity checks Yongseok Koh
2017-10-06 7:50 ` Nélio Laranjeiro
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 4/7] net/mlx5: separate shareable vector functions Yongseok Koh
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 5/7] net/mlx5: match Rx completion entry size to cacheline Yongseok Koh
2017-10-06 7:55 ` Nélio Laranjeiro
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 6/7] net/mlx5: fix configuration of Rx CQE compression Yongseok Koh
2017-10-06 7:57 ` Nélio Laranjeiro
2017-10-05 23:00 ` [dpdk-dev] [PATCH v1 7/7] net/mlx5: add vectorized Rx/Tx burst for ARM Yongseok Koh
2017-10-09 2:39 ` [dpdk-dev] [PATCH v1 0/7] " Ferruh Yigit
2017-10-09 7:45 ` Adrien Mazarguil [this message]
2017-10-09 17:40 ` Yongseok Koh
2017-10-09 18:19 ` Olga Shern
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 " Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 1/7] net/mlx5: cleanup memory barriers Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 2/7] net/mlx5: rename a file of SSE Rx/Tx Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 3/7] net/mlx5: use static assert for compile-time sanity checks Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 4/7] net/mlx5: separate shareable vector functions Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 5/7] net/mlx5: match Rx completion entry size to cacheline Yongseok Koh
2017-10-09 18:46 ` [dpdk-dev] [PATCH v2 6/7] net/mlx5: fix configuration of Rx CQE compression Yongseok Koh
2017-10-09 18:47 ` [dpdk-dev] [PATCH v2 7/7] net/mlx5: add vectorized Rx/Tx burst for ARM Yongseok Koh
2017-10-09 19:09 ` [dpdk-dev] [PATCH v2 0/7] " Ferruh Yigit
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=20171009074518.GE13551@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=rasland@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=xuemingl@mellanox.com \
--cc=yskoh@mellanox.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).