On Thursday July 24, a.p.zijlstra@chello.nl wrote:This looks quite different to last time I looked at the code (I think). You now have a more structured "kmalloc_reserve" interface which returns a flag to say if the allocation was from an emergency pool. I think this will be a distinct improvement at the call sites, though I haven't looked at them yet. :-) ^^^^^ .... I cannot figure out why the spinlock is being used to protect updates to 'limit'. As far as I can see, mem_reserve_mutex already protects all those updates. Certainly we need the spinlock for usage, but why for limit?? .... Why not just if (emerg) *emerg = 1. I can't we where '*emerg' can have any value but 0 or 1, so the '|' is pointless ??? Thanks, NeilBrown -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jesper Krogh | Re: Linux 2.6.26-rc4 |
| Thomas Gleixner | Re: Linux 2.6.21-rc1 |
| Hugh Dickins | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
git: | |
| Antonio Almeida | HTB accuracy for high speed |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
