[Click] transmit notification error

[John Bicket]

Hi Jennifer!
It's a new feature that I added a few weeks 
ago.  I checked in changes to eddie's linux svn repository, but I'm 
not sure how to generate patches for all the kernels. 

Instead of looping on dev->tbusy, this makes it so that todevice won't 
get scheduled when a device stoppes its transmit queue, and will wake up 
again the device calls netif_wake_queue.  Previously, it would just call 
hard_start_tx over and over again until a packet got through, meaning
you
would just burn up cpu waiting for the device to let you send, causing 
click to take up all the cpu.

I put the patch at http://18.26.4.9/~jbicket/todevice.linux.patch

If you don't have the patch, it works just like it did before, but it 
just prints out the warning, so you can ignore it.

John


Jennifer Albornoz Mulligan [mulligan at theory.csail.mit.edu] wrote:
>
>Hi,
>
>I'm trying to run some the basic UDPGEN.click script and running accross
>an error I'm not sure how to solve. It gives me an error of:
>
>While initializing 'u/td :: ToDevice':
>  warning: not compiled for a Click kernel with transmit notification
>  warning: can't get deb transmit notification: not compiled for a Click
>kernel
>
>When I go back and look at my configuration documents I find:
>(in config-linuxmodule.h.in)
>
>#undef HAVE_CLICK_KERNEL
>#undef HAVE_CLICK_KERNEL_TX_NOTIFY
>
>So I presume that something isn't compiled into the kernel, but I
>don't know what option to include. What do I need to do to get the
>transmission notification compiled with click?
>
>Thanks
>Jen
>_______________________________________________
>click mailing list
>click at amsterdam.lcs.mit.edu
>https://amsterdam.lcs.mit.edu/mailman/listinfo/click