From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, jerinj@marvell.com, Ori Kam <orika@nvidia.com>,
Liron Himi <lironh@marvell.com>,
Prasun Kapoor <pkapoor@marvell.com>
Subject: Re: [PATCH] regex/cn9k: remove rule compiler
Date: Mon, 26 Jun 2023 09:16:32 +0200 [thread overview]
Message-ID: <3654869.RUnXabflUD@thomas> (raw)
In-Reply-To: <20230625135713.228660d7@hermes.local>
25/06/2023 22:57, Stephen Hemminger:
> On Wed, 21 Jun 2023 21:03:00 +0530
> Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> > On Wed, Jun 21, 2023 at 7:36 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> > >
> > > Nobody knows how to build the feature.
> > > When the dependency "rxp_compiler" is found,
> > > the header file is not available:
> > >
> > > drivers/regex/cn9k/cn9k_regexdev_compiler.c:12:10: fatal error:
> > > rxp-compiler.h: No such file or directory
> > >
> > > It seems that it depends on a proprietay library.
> >
> > Yes. it depended on proprietary library owned by NVIDIA now. Not sure
> > Marvell has rights to publish it "freely available".
> > In order to avoid forking this library, better option to make this
> > library as public. Also, it looks like the library itself won't have
> > proper installation procedures that is the
> > reason for conflict as documented here in
> > https://bugs.dpdk.org/show_bug.cgi?id=1232.
>
> Interesting. Then what about the GPU support which currently requires
> proprietary NVIDIA CUDA library
CUDA can be downloaded.
It is even packaged in many Linux distributions.
next prev parent reply other threads:[~2023-06-26 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 14:06 [PATCH] regex/cn9k: remove rule compiler Thomas Monjalon
2023-06-21 15:33 ` Jerin Jacob
2023-06-25 20:57 ` Stephen Hemminger
2023-06-26 7:16 ` Thomas Monjalon [this message]
2023-06-26 16:22 ` Stephen Hemminger
2023-06-26 16:43 ` Thomas Monjalon
2023-06-26 17:11 ` Stephen Hemminger
2023-07-03 14:59 ` 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=3654869.RUnXabflUD@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=lironh@marvell.com \
--cc=orika@nvidia.com \
--cc=pkapoor@marvell.com \
--cc=stephen@networkplumber.org \
/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.