DPDK CI discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <maxime.coquelin@redhat.com>, dpdklab <dpdklab@iol.unh.edu>,
	Ali Alnubani <alialnu@nvidia.com>
Cc: <i.maximets@ovn.org>, <chenbo.xia@intel.com>,
	<xuan.ding@intel.com>, <cheng1.jiang@intel.com>,
	<liangma@liangbit.com>, Sunil Pai G <sunil.pai.g@intel.com>,
	Jiayu Hu <jiayu.hu@intel.com>, <dev@dpdk.org>,
	"ci@dpdk.org" <ci@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	"David Marchand" <david.marchand@redhat.com>,
	Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v4 1/1] vhost: integrate dmadev in asynchronous data-path
Date: Thu, 10 Feb 2022 20:50:44 +0000
Message-ID: <84e1506b-edf4-2428-c2c5-ce86d8adee07@intel.com> (raw)
In-Reply-To: <20220209125145.1918050-2-jiayu.hu@intel.com>

On 2/9/2022 12:51 PM, Jiayu Hu wrote:
> Since dmadev is introduced in 21.11, to avoid the overhead of vhost DMA
> abstraction layer and simplify application logics, this patch integrates
> dmadev in asynchronous data path.
> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> Signed-off-by: Sunil Pai G <sunil.pai.g@intel.com>

CI not run on this patch because it failed to apply [1].
(There is a build error with this patch but CI seems not able to catch
it because not able to apply it...)

Patch seems applied on top of 'main' repo [2].

Maxime, Ali, Lab,
In which tree should vhost (lib/vhost) patches be applied and tested?
main, next-net-virtio or next-net?


Applied on dpdk (0dff3f26d6faad4e51f75e5245f0387ee9bb0c6d)

       reply	other threads:[~2022-02-10 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220208104031.1885640-2-jiayu.hu@intel.com>
     [not found] ` <20220209125145.1918050-1-jiayu.hu@intel.com>
     [not found]   ` <20220209125145.1918050-2-jiayu.hu@intel.com>
2022-02-10 20:50     ` Ferruh Yigit [this message]
2022-02-10 21:01       ` Maxime Coquelin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84e1506b-edf4-2428-c2c5-ce86d8adee07@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=chenbo.xia@intel.com \
    --cc=cheng1.jiang@intel.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=i.maximets@ovn.org \
    --cc=jiayu.hu@intel.com \
    --cc=liangma@liangbit.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=sunil.pai.g@intel.com \
    --cc=thomas@monjalon.net \
    --cc=xuan.ding@intel.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git