mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Antti Halonen <antti.halonen@secgo.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: searching exported symbols from modules
Date: Wed, 19 Apr 2006 17:43:00 +0200	[thread overview]
Message-ID: <1145461380.3085.59.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <963E9E15184E2648A8BBE83CF91F5FAF5154E0@titanium.secgo.net>

On Wed, 2006-04-19 at 18:34 +0300, Antti Halonen wrote:
> Thanks for your persistence!
> 
> > but to what purpose?
> > what on earth do you need this for?
> > Again you talk about solutions not about the problem you're trying to
> > solve.
> 
> I have module which has set of algorithms. When I load my module, I will
> initialize my function pointer interface to point to these algorithms.
> And then go ahead and use my pointers trough the application...
> 
> This way I can easily add new algorithm implementations into my product
> and decide on the fly which ones to initialize into use.
>  
> Now. It happens that I have another module which offers algorithms I
> want to be able to use. So when I shoot up my module it should be able
> to initialize
> either the ones the external module offers or use the internal
> algorithms. In order to do this, I need to figure out on the fly if the
> other module is present, where it is, where I can find the function
> addresses...

a better way would be then to have a "core" module which is basically
collecting these algorithms, and then have the algorithm modules, when
they are loaded, register themselves with this core module. (and
unregister at unload). It's sort of inside-out with they way you're
trying to do it, but it'll work out a lot nicer. Obviously the user of
the algorithms can be another module in addition to this core module.
(and even register algorithms itself)
There's many examples in the kernel that work similar to this, for
example the crypto framework.



  reply	other threads:[~2006-04-19 15:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 15:34 Antti Halonen
2006-04-19 15:43 ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-20  7:15 Antti Halonen
2006-04-20  8:01 ` Kyle Moffett
2006-04-20 17:00 ` Adrian Bunk
2006-04-20  6:12 Antti Halonen
2006-04-20  7:00 ` Kyle Moffett
2006-04-20  5:50 Antti Halonen
2006-04-20  5:59 ` James Morris
2006-04-19 15:59 Antti Halonen
2006-04-19 16:02 ` Arjan van de Ven
2006-04-19 14:54 Antti Halonen
2006-04-19 15:17 ` Arjan van de Ven
2006-04-19 13:08 Antti Halonen
2006-04-19 14:55 ` linux-os (Dick Johnson)
2006-04-19 15:53 ` Robin Holt
2006-04-21  7:33 ` Keith Owens
2006-04-21 14:03   ` Vernon Mauery
2006-04-19 12:44 Antti Halonen
2006-04-19 12:59 ` linux-os (Dick Johnson)
2006-04-19 14:55   ` Jim Cromie
2006-04-19 14:22 ` Arjan van de Ven

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=1145461380.3085.59.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=antti.halonen@secgo.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®