From: David Marchand <david.marchand@redhat.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev <dev@dpdk.org>, Xiaolong Ye <xiaolong.ye@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Wei Zhao <wei.zhao1@intel.com>,
Aaron Conole <aconole@redhat.com>,
ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH v1 0/4] add Intel DCF PMD support
Date: Mon, 9 Mar 2020 16:36:54 +0100 [thread overview]
Message-ID: <CAJFAV8zBkKeSUMsAtNhiAS1mRGuRFdK_hN9fNQjCJPNXU_qHuQ@mail.gmail.com> (raw)
In-Reply-To: <20200309141437.11800-1-haiyue.wang@intel.com>
On Mon, Mar 9, 2020 at 3:22 PM Haiyue Wang <haiyue.wang@intel.com> wrote:
>
> A DCF (Device Config Function) based approach is proposed where a device
> bound to the device's VF0 can act as a sole controlling entity to exercise
> advance functionality (such as switch, ACL) for rest of the VFs.
>
> The DCF works as a standalone PMD to support this function, which shares the
> ice PMD flow control core function and the iavf virtchnl mailbox core module.
>
> This patchset is based on:
> [1] https://patchwork.dpdk.org/cover/66417/ update ice base code
The problem is that the CI(s) won't handle this.
Example for the robot: https://travis-ci.com/ovsrobot/dpdk/builds/152461907
Maybe we could add something as an annotation to the cover letter or
the first patch of a series so that the CI(s) can detect and try to be
intelligent?
--
David Marchand
next parent reply other threads:[~2020-03-09 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200309141437.11800-1-haiyue.wang@intel.com>
2020-03-09 15:36 ` David Marchand [this message]
2020-03-09 16:20 ` Ye Xiaolong
2020-03-09 17:57 ` Thomas Monjalon
2020-03-09 19:34 ` Kevin Traynor
2020-03-10 2:00 ` Wang, Haiyue
2020-03-10 7:48 ` Thomas Monjalon
2020-03-10 9:36 ` Ferruh Yigit
2020-03-10 14:11 ` Aaron Conole
2020-03-10 14:09 ` Aaron Conole
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=CAJFAV8zBkKeSUMsAtNhiAS1mRGuRFdK_hN9fNQjCJPNXU_qHuQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=beilei.xing@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=wei.zhao1@intel.com \
--cc=xiaolong.ye@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).