[Click] where click module binary image location ?

[Eddie Kohler]

Your understanding is incorrect.  click-install does not compile new
object code for each configuration.  Instead, the running click.ko
module parses the configuration file.

Eddie


2011/11/7 ahmed A. <amego83 at gmail.com>:
> I mean the the one which contains or follows the click configuration file
> created by the user , i.e. after you write your configuration file you
> use click-install start click inside the kernel. My understanding is that
> the click-install should create a binary image or code which can be
> executed by the kernel, the image should be like drivers images ending with
> .ko and located somewhere. I don't think /use/local/lib/click.ko is that
> image, because it doesn't change when you load a new configuration file
>  using click.install
>
>
>> 2011/11/4 kele kele <jinkelei87 at gmail.com>
>>
>>> Do you mean the click.ko and proclikefs.ko? If you install click default,
>>> the click imag is in /use/local/lib/click.ko
>>>
>>> 在 2011年11月3日星期四，ahmed A. <amego83 at gmail.com> 写道：
>>>
>>> > Hello everyone,
>>> >
>>> > Can anyone tell where the Click module binary image is located after it
>>> is
>>> > loaded to the kernel using Click-install. For example for the netwok
>>> driver
>>> > e1000
>>> > the binary image can be found at
>>> > /lib/module/2.6.18/kernel/driver/net/e1000/e1000.ko, so where click
>>> loaded
>>> > image is located ??????
>>> >
>>> > I need this image to attach it to oprofile to map the samples measured
>>> back
>>> > to the code ....
>>> >
>>> >
>>> > I would appreciate any help or tips .
>>> >
>>> > Bests,
>>> > Ahmed
>>> > _______________________________________________
>>> > click mailing list
>>> > click at amsterdam.lcs.mit.edu
>>> > https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>> >
>>
>>
>>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>