Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - ifconfig pause: (3 Items)
   
ifconfig pause  
Hi,

I'm trying io-pkt on a Dell Latitude D820 laptop running Neutrino natively in dual core mode. It's got a Broadcom GigE 
interface which works with io-net.

With io-pkt, I use the bge driver. Doing an

ifconfig bge0 192.168.51.116

was leading to a pause of roughly 1-2 seconds before the prompt returned. With the old io-net, an ifconfig did not 
introduce such a pause.

Is this expected behaviour? What is happening in this (very long, from a CPU speed point of view, although the CPU 
utilize graph did not go up) time? Many QNX Neutrino users care a lot about boot time being as quickly as possible and 
can not afford a 1-2 seconds pause.

Any feedback will be greatly appreciated.

Cheers,


Malte
Re: ifconfig pause  
On Fri, Nov 16, 2007 at 10:27:08AM -0500, Malte Mundt wrote:
> Hi,
> 
> I'm trying io-pkt on a Dell Latitude D820 laptop running Neutrino
> natively in dual core mode. It's got a Broadcom GigE interface which
> works with io-net.
> 
> With io-pkt, I use the bge driver. Doing an
> 
> ifconfig bge0 192.168.51.116
> 
> was leading to a pause of roughly 1-2 seconds before the prompt
> returned. With the old io-net, an ifconfig did not introduce such a
> pause.
> 
> Is this expected behaviour? What is happening in this (very long, from a
> CPU speed point of view, although the CPU utilize graph did not go up)
> time? Many QNX Neutrino users care a lot about boot time being as
> quickly as possible and can not afford a 1-2 seconds pause.
> 

In io-net 'ifconfig up / down' didn't actually enable /
disable the hardware (it set a flag in the stack marking it
as down but the hardware was still hot).  When you assign an
address it also does the equivalent of 'ifconfig up' so I
suspect it's probably during the hardware init phase with
this particular driver.

-seanb
Re: ifconfig pause  
Wow, that was a quick reply! And what you say makes complete sense. So for users who are concerned about boot speed, 
just using an '&' symbol to initialize in the background will be ok, I guess? Is there an equivalent for 

waitfor /dev/io-net/en0  

in io-pkt?

In older buildfiles I also saw

waitfor /dev/socket

Which one makes sense in combination with a 

ifconfig bge0 192.168.51.116 &  (<- starting it in the background)

do_something_that_does_not_need_network

waitfor... ?

do_something_that_needs_network

--

Cheers,


Malte