On Wed, 7 May 2008, Robin Holt wrote:You simply will *have* to do it without locally holding all the MM spinlocks. Because quite frankly, slowing down all the normal VM stuff for some really esoteric hardware simply isn't acceptable. We just don't do it. So what is it that actually triggers one of these events? The most obvious solution is to just queue the affected pages while holding the spinlocks (perhaps locking them locally), and then handling all the stuff that can block after releasing things. That's how we normally do these things, and it works beautifully, without making everything slower. Sometimes we go to extremes, and actually break the locks are restart (ugh), and it gets ugly, but even that tends to be preferable to using the wrong locking. The thing is, spinlocks really kick ass. Yes, they restrict what you can do within them, but if 99.99% of all work is non-blocking, then the really odd rare blocking case is the one that needs to accomodate, not the rest. Linus --
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Linus Torvalds | Linux 2.6.27-rc8 |
| Adrian Bunk | 2.6.23-rc4-mm1: mips compile error |
| Nick Piggin | Re: [PATCH 0 of 4] Generic AIO by scheduling stacks |
git: | |
| Bill Lear | Dangers of working on a tracking branch |
| Pedro Melo | Re: git on MacOSX and files with decomposed utf-8 file names |
| Linus Torvalds | Re: kernel.org mirroring (Re: [GIT PULL] MMC update) |
| Junio C Hamano | Re: [Census] So who uses git? |
| Leon Dippenaar | New tcp stack attack |
| Richard Stallman | Real men don't attack straw men |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Chris | sudo & wheel group |
| Paul Moore | [PATCH v7 00/17] Labeled networking patches for 2.6.28 |
| Wang Chen | [PATCH 2/15] netdevice 82596: Convert directly reference of netdev->priv to net... |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: csum offload and af_packet |
