All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Liron Himi <lironh@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Sharing Common libs between PMDs
Date: Wed, 14 Mar 2018 20:25:45 +0530	[thread overview]
Message-ID: <20180314145538.GA2482@jerin> (raw)
In-Reply-To: <f3d9b6d6562c41258fecb14a54a90565@IL-EXCH02.marvell.com>

-----Original Message-----
> Date: Wed, 14 Mar 2018 09:34:40 +0000
> From: Liron Himi <lironh@marvell.com>
> To: "dev@dpdk.org" <dev@dpdk.org>
> CC: Liron Himi <lironh@marvell.com>
> Subject: [dpdk-dev] Sharing Common libs between PMDs
> 
> Hi,
> 
> We have several PMDs in DPDK that are using the same underlying common libraries.
> In addition, we have plans to add some new common service into DPDK that already introduces too much complexity with the way that the code is written now.
> Therefore, we would like to move all our common functions calls into one shared/common folder in DPDK and we need to find proper place for this purpose.
> 
> Can you suggest on such a place?

There was an attempt to create "driver/common" but latter the common code
for NXP HW device got moved to drivers/bus/dpaa/. Linux kernel has
something called "driver/soc", I think, "driver/soc" may be more appropriate.

Currently DPDK's driver build dependency is in the following order
(bus, mempool, net, crypto, event).
Other than driver/common or driver/soc, one option could be to
- Move the common code to bus or mempool
and
- Across the drivers, include the header files through CFLAGS if the common code
  is in header file
http://dpdk.org/browse/dpdk/tree/drivers/event/octeontx/Makefile#n13

> 
> Regards,
> Liron
> 
> 
> 

  reply	other threads:[~2018-03-14 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  9:34 Sharing Common libs between PMDs Liron Himi
2018-03-14 14:55 ` Jerin Jacob [this message]
2018-03-14 15:04   ` Bruce Richardson
2018-03-14 16:11     ` Trahe, Fiona
2018-03-14 17:38       ` Shreyansh Jain
2018-03-14 17:50         ` Jerin Jacob
2018-03-14 18:13           ` Trahe, Fiona
2018-03-15  6:58             ` Hemant Agrawal

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=20180314145538.GA2482@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=lironh@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 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.