From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Harman Kalra <hkalra@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx2: fix PTP enable via Rx ofload flags
Date: Sun, 28 Jul 2019 16:24:13 +0000 [thread overview]
Message-ID: <BYAPR18MB2424A92253A894C5D0AAE408C8C20@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1564235652-29983-1-git-send-email-hkalra@marvell.com>
> -----Original Message-----
> From: Harman Kalra <hkalra@marvell.com>
> Sent: Saturday, July 27, 2019 7:26 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar
> Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar Kokkilagadda
> <kirankumark@marvell.com>
> Cc: dev@dpdk.org; Harman Kalra <hkalra@marvell.com>
> Subject: [PATCH v2] net/octeontx2: fix PTP enable via Rx ofload flags
>
> Earlier implementation for enabling ptp via RX offload flag was causing
> segmentation fault as it was getting executed in the device configuration
> stage where RX and TX queues were not configured. As in the ptp enable
> process rx queues are used for mbuf setup while tx queues are used for
> send descriptor setup.
> Moving the logic in dev start as all the resources will be configured.
>
> Fixes: b5dc3140448ee ("net/octeontx2: support base PTP")
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
prev parent reply other threads:[~2019-07-28 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 15:30 [dpdk-dev] [PATCH] " Harman Kalra
2019-07-27 13:56 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2019-07-28 16:24 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB2424A92253A894C5D0AAE408C8C20@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@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).