Messages in this thread |  | | | Date | Tue, 12 Feb 2008 14:19:41 -0800 | | From | Andrew Morton <> | | Subject | Re: [PATCH v2] Execute tasklets in the same order they were queued |
| |
On Tue, 12 Feb 2008 16:06:47 -0600 Olof Johansson <olof@lixom.net> wrote:
> I noticed this when looking at an openswan issue. Openswan (ab?)uses > the tasklet API to defer processing of packets in some situations, > with one packet per tasklet_action(). I started noticing sequences > of backwards-ordered sequence numbers coming over the wire, since > new tasklets are always queued at the head of the list but processed > sequentially. > > Convert it to instead append new entries to the tail of the list. As an > extra bonus, the splicing code in takeover_tasklets() no longer has to > iterate over the list.
hm, well, let's see what if any effect this has on networking.
I'll cheerily tag this as to-be-merged-via-git-sched. Ingo wasn't doing much anyway.
|  |