DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Jan Mędala" <jan@semihalf.com>
Cc: dev@dpdk.org, Alexander Matushevsky <matua@amazon.com>
Subject: Re: [dpdk-dev] [PATCH v8 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)
Date: Fri, 18 Mar 2016 17:19:28 +0000	[thread overview]
Message-ID: <20160318171928.GD13720@bricha3-MOBL3> (raw)
In-Reply-To: <CANw_3Zei-crwUhj9hZV9HJeMKsgFk8sCXgQhrHo4LOyf=baOjA@mail.gmail.com>

On Fri, Mar 18, 2016 at 06:11:29PM +0100, Jan Mędala wrote:
> Great news!
> We are going to extend functionality of the ENA PMD, so from now I will
> send patches based on v8 version.
> 
More specifically, please base any further patches on the code on
dpdk-next-net/rel_16_04 branch. At this stage in the release cycle for 16.04,
no new feature patches can be accepted, only bug-fixes. Feel free to send
RFC patches for 16.07 release though, to add any new features.

/Bruce

> Thanks,
> 
>   Jan
> 
> 2016-03-18 18:04 GMT+01:00 Bruce Richardson <bruce.richardson@intel.com>:
> 
> > On Thu, Mar 17, 2016 at 03:31:14PM +0100, Jan Medala wrote:
> > > v3:
> > > Additional features for Amazon ENA:
> > > * Low Latenycy Queue (LLQ) for Tx
> > > * RSS
> > > v4:
> > > * Improved doc
> > > * Improved style according to checkpatch script
> > > * Fixed build problems on: i686, clang, +shared, +debug
> > > v5:
> > > * Removed 'cvos' environment code from ena Makefile
> > > * Driver symbol version fixed to DPDK_16.04
> > > * Max MTU is read from device attributes
> > > v6:
> > > * Updated ENA communication layer
> > > * Added check if DPDK queue size is supported by device
> > > * Checkpatch results: 6 warns >80, 0 warns >90, no whitespace issues
> > > * defined likely/unlikely (can compile with ARM toolchain)
> > > * Updated doc/guides/nics/overview.rst w/ ENA
> > > * Removed metioned #pragma for "-Wcast-qual"
> > > v7:
> > > * Resolved Thomas's comments:
> > >   - included <rte_branch_prediction.h> instead of own definition of
> > >     likely/unlikely
> > >   - used RTE_MIN/RTE_MAX macros
> > > v8:
> > > * Fixed init (error) logging to be always available
> > >
> > > Jan Medala (4):
> > >   ena: Amazon ENA documentation
> > >   ena: Amazon ENA communication layer
> > >   ena: Amazon ENA communication layer for DPDK platform
> > >   ena: DPDK polling-mode driver for Amazon Elastic Network Adapters
> > >     (ENA)
> > >
> > Applied to dpdk-next-net/rel_16_04.
> >
> > Thanks for the contribution of a new PMD.
> >
> > /Bruce
> >

      reply	other threads:[~2016-03-18 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 14:31 Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 1/4] ena: Amazon ENA documentation Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 2/4] ena: Amazon ENA communication layer Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 3/4] ena: Amazon ENA communication layer for DPDK platform Jan Medala
2016-03-17 14:31 ` [dpdk-dev] [PATCH v8 4/4] ena: DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-03-18 17:17   ` Bruce Richardson
2016-03-21 17:33   ` Stephen Hemminger
2016-03-18 17:04 ` [dpdk-dev] [PATCH v8 0/4] " Bruce Richardson
2016-03-18 17:11   ` Jan Mędala
2016-03-18 17:19     ` Bruce Richardson [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=20160318171928.GD13720@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jan@semihalf.com \
    --cc=matua@amazon.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).