All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Kantee <pooka-X3B1VOXEql0@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] eal: add support for shared object drivers
Date: Wed, 12 Jun 2013 14:58:13 +0200	[thread overview]
Message-ID: <51B87065.2020600@iki.fi> (raw)
In-Reply-To: <51B87027.40703-D3plGOiwsub1KXRcyAk9cg@public.gmane.org>

On 12.06.2013 09:51, Thomas Monjalon wrote:
 > From: Damien Millescamps <damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
 >
 > Add an option to specify libraries to be loaded before probing the PCI.
 >
 > For instance, testpmd -d librte_pmd_xxx.so can be used to enable xxx 
driver
 > support on testpmd without any recompilation of testpmd.

What's the use case?  Unless I'm missing something, testpmd still needs 
an explicit rte_pmd_foo_init() call.  It's of course not difficult to 
sprinkle some __attribute__((constructor))'s into the pmd's, but without 
doing that (or something equivalent), what's the purpose of the change?

  parent reply	other threads:[~2013-06-12 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  7:51 [PATCH] eal: add support for shared object drivers Thomas Monjalon
     [not found] ` <1371023487-23617-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-06-12 11:55   ` Olivier MATZ
     [not found]     ` <51B861CA.8060203-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-06-12 15:12       ` Thomas Monjalon
     [not found] ` <51B87027.40703@cs.hut.fi>
     [not found]   ` <51B87027.40703-D3plGOiwsub1KXRcyAk9cg@public.gmane.org>
2013-06-12 12:58     ` Antti Kantee [this message]
     [not found]       ` <51B87065.2020600-X3B1VOXEql0@public.gmane.org>
2013-06-12 14:54         ` Olivier MATZ
     [not found]           ` <51B88BA7.9080605-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-06-12 15:12             ` Antti Kantee

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=51B87065.2020600@iki.fi \
    --to=pooka-x3b1voxeql0@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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.