DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] octeontx: sync with latest SDK
Date: Thu, 21 Nov 2019 08:10:16 +0530	[thread overview]
Message-ID: <CALBAE1MheBSuQdQU8eC8hSdgDS9yh8yggpdJ7d5GfGug0-eTDQ@mail.gmail.com> (raw)
In-Reply-To: <20191120034808.2760-1-pbhagavatula@marvell.com>

On Wed, Nov 20, 2019 at 9:18 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Sync octeontx mailbox with the latest version (10.1.2.x) of SDK available.


Series applied to dpdk-next-eventdev/master. Thanks.

>
> Pavan Nikhilesh (6):
>   octeontx: update mbox definition to version 1.1.3
>   net/octeontx: add application domain validation
>   net/octeontx: cleanup redudant mbox structs
>   mempool/octeontx: add application domain validation
>   event/octeontx: add appication domain validation
>   net/octeontx: make Rx queue offloads same as dev offloads
>
>  doc/guides/eventdevs/octeontx.rst             |   7 +
>  doc/guides/nics/octeontx.rst                  |   7 +
>  drivers/common/octeontx/octeontx_mbox.c       | 112 +++++++-
>  drivers/common/octeontx/octeontx_mbox.h       |  13 +-
>  .../octeontx/rte_common_octeontx_version.map  |   7 +
>  drivers/event/octeontx/ssovf_evdev.c          |   5 +-
>  drivers/event/octeontx/ssovf_probe.c          |   7 +-
>  drivers/event/octeontx/timvf_evdev.c          |  12 +-
>  drivers/event/octeontx/timvf_evdev.h          |   8 +-
>  drivers/event/octeontx/timvf_probe.c          |  65 +++--
>  drivers/mempool/octeontx/octeontx_fpavf.c     |  87 ++++--
>  drivers/net/octeontx/base/octeontx_bgx.h      |   3 +
>  drivers/net/octeontx/base/octeontx_pkivf.c    |  83 +++++-
>  drivers/net/octeontx/base/octeontx_pkivf.h    | 249 +++---------------
>  drivers/net/octeontx/base/octeontx_pkovf.c    |  37 ++-
>  drivers/net/octeontx/base/octeontx_pkovf.h    |   3 +
>  drivers/net/octeontx/octeontx_ethdev.c        |  15 +-
>  drivers/net/octeontx/octeontx_ethdev.h        |   1 +
>  18 files changed, 418 insertions(+), 303 deletions(-)
>
> --
> 2.17.1
>

      parent reply	other threads:[~2019-11-21  2:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  3:48 pbhagavatula
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 1/6] octeontx: update mbox definition to version 1.1.3 pbhagavatula
2020-05-01 15:40   ` Ferruh Yigit
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 2/6] net/octeontx: add application domain validation pbhagavatula
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 3/6] net/octeontx: cleanup redudant mbox structs pbhagavatula
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 4/6] mempool/octeontx: add application domain validation pbhagavatula
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 5/6] event/octeontx: add appication " pbhagavatula
2019-11-20  3:48 ` [dpdk-dev] [PATCH v2 6/6] net/octeontx: make Rx queue offloads same as dev offloads pbhagavatula
2019-11-21  2:40 ` Jerin Jacob [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=CALBAE1MheBSuQdQU8eC8hSdgDS9yh8yggpdJ7d5GfGug0-eTDQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.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).