There is one idea that seems to model this cleanly without breaking all kinds of expectations. That is an irq with a very small data payload. In that case we wire all of the vectors up to a single irq handler that computes the payload as: payload = vector - base-vector. And then we figure out how to pass that to the handler in irqaction. To most of the system it is a single irq so it avoids breaking expectations about what an irq is. To everything else it is a little odd, and has it's own unique set of rules (which is good as well). Eric --
| Andrew Morton | -mm merge plans for 2.6.23 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mel Gorman | [PATCH 6/8] x86_64 - Specify amount of kernel memory at boot time |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem) |
