From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/sfc: add missing Rx descriptor status callback
Date: Wed, 30 May 2018 10:42:15 +0100 [thread overview]
Message-ID: <b365e95b-528d-6a14-8299-ac63f98b8e41@intel.com> (raw)
In-Reply-To: <54455a54-fef1-8ad7-0bea-6c864bc4cbbe@solarflare.com>
On 5/30/2018 7:44 AM, Andrew Rybchenko wrote:
> Thomas, Ferruh,
>
> I've found out that the following patch is deferred in patchwork:
> https://dpdk.org/dev/patchwork/patch/40455/
>
> It is critical under certain conditions since fix application crash.
> The patch is net/sfc local and just few lines - absolutely harmless.
> The only potential DPDK-wide effect is build, but the patch is really
> trivial and it is hard to imagine how it could affect the build.
> I'd like it to be included in 18.05, if possible.
>
> I understand that 18.05 is really very-very late already and it
> could be too late even for such patch. Just would like to
> double-check it.
Hi Andrew,
I did mark it as deferred and I overlooked that this fixes a crash.
Agree that scope is local and only effect should be build, I confirmed the build
but to be sure I suggest get the patch and trigger an Intel daily build, and
include the patch into release if only that build also returns success.
>
> Thanks,
> Andrew.
>
> On 05/28/2018 09:50 AM, Andrew Rybchenko wrote:
>> Rx descriptor status callback was lost and request of the Rx
>> descriptor status crashes application if equal stride super-buffer
>> Rx mode is used.
>>
>> Fixes: 390f9b8d82c9 ("net/sfc: support equal stride super-buffer Rx mode")
>>
>> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
>> ---
>> drivers/net/sfc/sfc_ef10_essb_rx.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/net/sfc/sfc_ef10_essb_rx.c b/drivers/net/sfc/sfc_ef10_essb_rx.c
>> index 289b61e52..5f5af602c 100644
>> --- a/drivers/net/sfc/sfc_ef10_essb_rx.c
>> +++ b/drivers/net/sfc/sfc_ef10_essb_rx.c
>> @@ -413,6 +413,14 @@ sfc_ef10_essb_rx_qdesc_npending(__rte_unused struct sfc_dp_rxq *dp_rxq)
>> return -ENOTSUP;
>> }
>>
>> +static sfc_dp_rx_qdesc_status_t sfc_ef10_essb_rx_qdesc_status;
>> +static int
>> +sfc_ef10_essb_rx_qdesc_status(__rte_unused struct sfc_dp_rxq *dp_rxq,
>> + __rte_unused uint16_t offset)
>> +{
>> + return -ENOTSUP;
>> +}
>> +
>> static sfc_dp_rx_get_dev_info_t sfc_ef10_essb_rx_get_dev_info;
>> static void
>> sfc_ef10_essb_rx_get_dev_info(struct rte_eth_dev_info *dev_info)
>> @@ -687,5 +695,6 @@ struct sfc_dp_rx sfc_ef10_essb_rx = {
>> .qpurge = sfc_ef10_essb_rx_qpurge,
>> .supported_ptypes_get = sfc_ef10_supported_ptypes_get,
>> .qdesc_npending = sfc_ef10_essb_rx_qdesc_npending,
>> + .qdesc_status = sfc_ef10_essb_rx_qdesc_status,
>> .pkt_burst = sfc_ef10_essb_recv_pkts,
>> };
>
next prev parent reply other threads:[~2018-05-30 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 6:50 Andrew Rybchenko
2018-05-30 6:44 ` Andrew Rybchenko
2018-05-30 9:42 ` Ferruh Yigit [this message]
2018-05-30 10:30 ` Thomas Monjalon
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=b365e95b-528d-6a14-8299-ac63f98b8e41@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.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).