From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Yongseok Koh <yskoh@mellanox.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Luca Boccassi <bluca@debian.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] build: disable armv8 crypto extension
Date: Tue, 7 May 2019 07:59:14 +0000 [thread overview]
Message-ID: <BYAPR18MB2424305090CD8C3E65F85212C8310@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Message-ID: <20190507075914.YxTXs1TGEYFsyF9vOLJ9UiT6hyYtSeXzk5IBlVibTgc@z> (raw)
In-Reply-To: <B85DB924-5B3D-419E-8A20-CD88BD47181A@mellanox.com>
> -----Original Message-----
> From: Yongseok Koh <yskoh@mellanox.com>
> Sent: Tuesday, May 7, 2019 3:17 AM
> To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Thomas Monjalon
> <thomas@monjalon.net>; dev@dpdk.org; bruce.richardson@intel.com;
> Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Shahaf Shuler
> <shahafs@mellanox.com>; Gavin Hu (Arm Technology China)
> <Gavin.Hu@arm.com>; stable@dpdk.org; Luca Boccassi
> <bluca@debian.org>; nd <nd@arm.com>
> Subject: [EXT] Re: [dpdk-stable] [PATCH v2] build: disable armv8 crypto
> extension
>
> > On May 3, 2019, at 10:50 AM, Yongseok Koh <yskoh@mellanox.com>
> wrote:
> >
> >> I think this change might have an impact on the existing users. Does
> >> this change need to be documented somewhere (at least in the release
> notes)?
> >
> > Practically, there would be no impact. Even if user's app makes use of
> > crypto instructions, the build config of the app should have the flag.
>
> On IRC, I could see you concerned about the case where user app derives
> build flags from DPDK like apps under the examples directory. Yes, that's a
> valid concern.
Is there any DPDK example application would depend on the armv8 crypto flags? IMO, None of
the applications are directly using armv8 crypto instruction. Even such as comes for any external DPDK
app which is not in dpdk.org tree then it can be added in APP makefile.
IMO, app writes should be aware of the need for using +crypto if he/she using the crypto instruction.
>
> Thomas/Jerin, where could be the best spot to document it? Just release
> note?
> I think release note would be fine.
next prev parent reply other threads:[~2019-05-07 7:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 1:58 [dpdk-dev] [PATCH 1/2] build: add option for " Yongseok Koh
2019-05-02 1:58 ` Yongseok Koh
2019-05-02 1:58 ` [dpdk-dev] [PATCH 2/2] mk: disable armv8 crypto extension for Mellanox BlueField Yongseok Koh
2019-05-02 1:58 ` Yongseok Koh
2019-05-02 4:12 ` Honnappa Nagarahalli
2019-05-02 4:12 ` Honnappa Nagarahalli
2019-05-02 5:40 ` Yongseok Koh
2019-05-02 5:40 ` Yongseok Koh
2019-05-03 4:01 ` Honnappa Nagarahalli
2019-05-03 4:01 ` Honnappa Nagarahalli
2019-05-02 4:13 ` [dpdk-dev] [PATCH 1/2] build: add option for armv8 crypto extension Honnappa Nagarahalli
2019-05-02 4:13 ` Honnappa Nagarahalli
2019-05-02 5:46 ` Yongseok Koh
2019-05-02 5:46 ` Yongseok Koh
2019-05-02 10:00 ` Jerin Jacob Kollanukkaran
2019-05-02 10:00 ` Jerin Jacob Kollanukkaran
2019-05-03 3:57 ` Honnappa Nagarahalli
2019-05-03 3:57 ` Honnappa Nagarahalli
2019-05-03 9:57 ` Yongseok Koh
2019-05-03 9:57 ` Yongseok Koh
2019-05-03 12:28 ` [dpdk-dev] [PATCH v2] build: disable " Yongseok Koh
2019-05-03 12:28 ` Yongseok Koh
2019-05-03 15:02 ` Honnappa Nagarahalli
2019-05-03 15:02 ` Honnappa Nagarahalli
2019-05-03 16:10 ` Honnappa Nagarahalli
2019-05-03 16:10 ` Honnappa Nagarahalli
2019-05-03 17:50 ` Yongseok Koh
2019-05-03 17:50 ` Yongseok Koh
2019-05-06 21:46 ` [dpdk-dev] [dpdk-stable] " Yongseok Koh
2019-05-06 21:46 ` Yongseok Koh
2019-05-07 7:59 ` Jerin Jacob Kollanukkaran [this message]
2019-05-07 7:59 ` Jerin Jacob Kollanukkaran
2019-05-07 11:03 ` Honnappa Nagarahalli
2019-05-07 11:03 ` Honnappa Nagarahalli
2019-05-07 12:02 ` Jerin Jacob Kollanukkaran
2019-05-07 12:02 ` Jerin Jacob Kollanukkaran
2019-05-03 22:13 ` [dpdk-dev] " Dharmik Thakkar
2019-05-03 22:13 ` Dharmik Thakkar
2019-05-06 21:41 ` Yongseok Koh
2019-05-06 21:41 ` Yongseok Koh
2019-05-07 21:11 ` [dpdk-dev] [PATCH v3] " Yongseok Koh
2019-05-07 21:11 ` Yongseok Koh
2019-05-13 19:26 ` Honnappa Nagarahalli
2019-05-13 19:26 ` Honnappa Nagarahalli
2019-06-03 23:11 ` 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=BYAPR18MB2424305090CD8C3E65F85212C8310@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).