From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Michal Krawczyk <mk@semihalf.com>, dev@dpdk.org
Cc: gtzalik@amazon.com, mw@semihalf.com, matua@amazon.com,
mba@semihalf.com, igorch@amazon.com
Subject: Re: [dpdk-dev] [PATCH 2/2] net/ena: add support for RX_OFFSET feature
Date: Fri, 10 Jan 2020 10:32:30 +0000 [thread overview]
Message-ID: <164c579c-6ee5-3eda-2bb6-eafc80f826d3@intel.com> (raw)
In-Reply-To: <20191213133216.23572-3-mk@semihalf.com>
On 12/13/2019 1:32 PM, Michal Krawczyk wrote:
> From: Maciej Bielski <mba@semihalf.com>
>
> Allow the data in the first buffer to be shifted by `pkt_offset` after
> the header room. The offset value is provided by `ena_rx_ctx`.
>
> As part of this update, the version of the ENA was upgraded to v2.0.3.
>
> Signed-off-by: Maciej Bielski <mba@semihalf.com>
> Acked-by: Michal Krawczyk <mk@semihalf.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-01-10 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:32 [dpdk-dev] [PATCH 0/2] net/ena: add support for Rx offsets Michal Krawczyk
2019-12-13 13:32 ` [dpdk-dev] [PATCH 1/2] net/ena: upgrade HAL for new HW features Michal Krawczyk
2019-12-13 16:34 ` Stephen Hemminger
2019-12-13 20:01 ` Michał Krawczyk
2020-01-09 14:27 ` Ferruh Yigit
2020-01-09 15:26 ` Michał Krawczyk
2020-01-09 14:30 ` Ferruh Yigit
2020-01-09 15:39 ` [dpdk-dev] [PATCH v2 " Michal Krawczyk
2020-01-10 9:04 ` Ferruh Yigit
2020-01-10 9:39 ` Michał Krawczyk
2020-01-10 10:32 ` Ferruh Yigit
2019-12-13 13:32 ` [dpdk-dev] [PATCH 2/2] net/ena: add support for RX_OFFSET feature Michal Krawczyk
2020-01-10 10:32 ` Ferruh Yigit [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=164c579c-6ee5-3eda-2bb6-eafc80f826d3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=matua@amazon.com \
--cc=mba@semihalf.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.