aboutsummaryrefslogtreecommitdiff
path: root/Documentation/i2c/busses/i2c-piix4
diff options
context:
space:
mode:
authorOlof Johansson <olof@lixom.net>2008-03-04 15:23:25 -0800
committerIngo Molnar <mingo@elte.hu>2008-04-19 19:44:58 +0200
commit48f20a9a9488c432fc86df1ff4b7f4fa895d1183 (patch)
tree987a41075c8a6640968b6b2054306644e10e4933 /Documentation/i2c/busses/i2c-piix4
parentac086bc22997a2be24fc40fc8d46522fe7e03d11 (diff)
tasklets: execute tasklets in the same order they were queued
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. Signed-off-by: Olof Johansson <olof@lixom.net> Cc: "David S. Miller" <davem@davemloft.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/i2c/busses/i2c-piix4')
0 files changed, 0 insertions, 0 deletions