What I meant was that I modified the device driver to do what my element was supposed to do. So just after the DMA transfer is done from the device into the main memory, I perform the necessary operation on the packets.
Mythili Vutukuru wrote: >> I had a similar requirement. I just modified the device driver to >> reduce the latency to suit my needs. >> > But in my case, the latency between the NIC and the driver is minimal. > Most of the delay is after FromDevice has the packet but does not release > it to the downstream click elements. > > Mythili > >> >> Mythili Vutukuru wrote: >>> Hi, >>> I am running click version 1.5.0. The application I am building requires >>> that the delay between the network interface receiving the packet and my >>> custom click element processing the packet be minimum. Currently, the >>> FromDevice element queues up packets at interrupt time, and pushes them >>> out of its output when the task in the element is scheduled. I want to >>> reduce this delay. First question: is there any obvious way to do this? >>> I tried increasing the tickets of FromDevice using ScheduleInfo, but it >>> did not help. >>> >>> An obvious (but possibly flawed) approach I thought of is the following: >>> make FromDevice push out the packets at interrupt time itself to other >>> elements downstream. Second question: does running some click element >>> code at interrupt time break anything fundamental in the click >>> architecture? >>> >>> Thanks a lot, any help is much appreciated. >>> >>> Mythili >>> >>> >>> _______________________________________________ >>> click mailing list >>> click@amsterdam.lcs.mit.edu >>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >>> >> > > _______________________________________________ click mailing list click@amsterdam.lcs.mit.edu https://amsterdam.lcs.mit.edu/mailman/listinfo/click
