Title: [Sisuite-devel] RE: e100 slowness with trunk
I have tested previous versions of SystemImager (3.6.x) and did not have this problem - any clues as to what is causing this (new) issue?  (it's the same card I have been testing for the longest time, first time I've encountered such slow downs...)
 
I think I remember testing Brian's udev branch as well and didn't hit this problem.
 
(I have not ruled out hardware issue yet, but I don't think that's the case...)
 
Thanks,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Bernard Li
Sent: Mon 27/03/2006 16:38
To: [EMAIL PROTECTED]
Cc: sisuite-devel@lists.sourceforge.net; Brian Elliott Finley
Subject: [Sisuite-devel] RE: e100 slowness with trunk

> That's because all the available networks drivers are compiled
> statically into the kernel.. but the kernel should be able to
> probe and
> use only the correct one...
>
> As discussed with Brian the network drivers are needed into the kernel
> to reach the image server, then additional supports are
> provided by the
> boel_binaries.tar.gz.
>
> Another solution could be to compile all as modules and store all that
> modules into the initrd, but the big disadvantage of this approach
> reduces the scalability. In fact kernel+initrd can be pulled by the
> clients only via TFTP, so they can't exploit other nice
> transports, like
> multicast or bittorrent.
>
> There would be a 3rd solution... compile all as modules and split the
> network modules (stored into the initrd) and the other ones (stored in
> boel_binaries)... it should not be so difficult but it needs some work
> to do... what do you think?

I think either way is fine...  but I just don't understand why e100
doesn't work for me...

I just built SystemImager 3.7.2 x86_64 and it works fine with e1000 so
it seems that I'm having issues with that particular NIC...

> > I think the function "autodetect_hardware_and_load_modules()" in
> > "functions" is no longer necessary, I'll work on removing that as
> > well as other references to "discover".
> >
>
> This feature now should be included into the hotplug stuff... but I'm
> not sure... we need some tests...

I just tried to compile it _without_ the discover bits and it did not
correctly install the modules (eg. sd_mod was not installed).  Do we
need to make specific hotplug calls or should it automatically detect
and setup all the modules?

You're right, I think we still need some tests... ;-)

Cheers,

Bernard

P.S. Anyways, I think the code in trunk now works with x86 and x86_64,
and I think Brian is working on ia64...  any takers on ppc?


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to