Messages in this thread | | | Date | Mon, 8 Mar 2004 19:34:01 +0100 | From | Pavel Machek <> | Subject | Re: Some highmem pages still in use after shrink_all_memory()? |
| |
Hi!
> > > Note that there are some applications for which it is a *bug* if an > > > mlocked page gets written out to magnetic media. (gpg, for example.) > > > > mlock() does not guarantee things not hitting magnetic media, just as > > mlock() doesn't guarantee that the physical address of a page doesn't > > change. mlock guarantees that you won't get hard pagefaults and that you > > have guaranteed memory for the task at hand (eg for realtime apps and > > oom-critical stuff) > > Well, that's fine -- you can certainly define mlock to have whatever > semantics you want. But the semantics that gpg depends on are > reasonable, and if mlock is changed to have other semantics, there > should be some way for apps to get the behavior that used to be > implemented by mlock (and *documented* in the mlock man page). > > It's a pity that mlock doesn't take a flags argument.
How would it help?
Block system-wide suspend because 4K are mlocked? Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |