DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Stephen Hemminger <stephen@networkplumber.org>, thomas@monjalon.net
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK techboard minutes for 19th of December
Date: Thu, 17 Jan 2019 18:28:41 +0000	[thread overview]
Message-ID: <1547749721.4501.107.camel@debian.org> (raw)
In-Reply-To: <20190117094924.1fa8148b@hermes.lan>

On Thu, 2019-01-17 at 09:49 -0800, Stephen Hemminger wrote:
> Meeting notes for the DPDK technical board meeting held on 2019-12-19
> Sorry for the belated minutes, but the puppy hair killed my desktop
> ;-)
> 
> Attendees: 6/9
> 	- Thomas Monjalon
> 	- Bruce Richardson
> 	- Ferruh Yigit
> 	- Maxime Coquelin
> 	- Olivier Matz
> 	- Stephen Hemminger
> 
> KNI
> The existing KNI device is getting trimmed for 19.02.
> Consensus this is good, and hope is that KNI can get more work
> to improve performance (currently virtio is faster).
> 
> Build System
> Still not enough automated build and testing is done on DPDK patches.
> Investigating getting Open Build Service (SUSE) as continuous build
> service
> to check all patches on all architectures. Luca will do more
> investigation.

https://build.opensuse.org/package/show/home:bluca:dpdk/dpdk

I've already linked it a few times - it works and builds for various
architectures/distro combinations. GCC only at the moment - RPM using
legacy makefiles, DEB using meson. With more time and work it could
become a full matrix meson/make gcc/clang if desired.

Triggering a source refresh picks up the latest master commit. It would
be pretty simple to automate as a post-receive hook. It can also send
emails on failures with log snippets.

Note that testing not-yet-merged patches on patchwork, although
possible, would require a non-trivial amount of work to integrate.

Let me know if you want to bring this forward or need more info.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2019-01-17 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 17:49 Stephen Hemminger
2019-01-17 18:28 ` Luca Boccassi [this message]

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=1547749721.4501.107.camel@debian.org \
    --to=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).