[Click] Scheduling ToDevice
Cliff Frey
cliff at meraki.com
Tue Jun 1 13:06:38 EDT 2010
Perhaps you could add a BURST-type parameter to FromDevice to allow it to
process multiple packets at once, therefore favoring receive? I'm not sure
how easily this could be done while making sure that the fromdevice.cc code
doesn't block... but perhaps it is as easy as changing the "1" argument to
pcap_dispatch to be a higher number.
Cliff
On Tue, Jun 1, 2010 at 2:53 AM, Harald Schiöberg <
harald at net.t-labs.tu-berlin.de> wrote:
> Hi,
>
> following problem with userlevel:
>
> If click is CPU-bound and we always have packets to send,
> then the ToDevice::run_task will call _task.fast_reschedule() all the
> time, giving no cpu at all to the ingress processing.
>
> This is good behaviour for IP forwarding ( deliver before spending cpu
> on receiving),
> but I need to prioritize input processing over output.
> ( I need to process control-frames to stop sending )
>
>
> I tried to replace _task.fast_reschedule() with _task.reschedule() but
> that does solve it. Any suggestions ?
>
> Harald
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>
More information about the click
mailing list