Messages in this thread | | | Date | Sat, 19 Jul 2003 09:05:57 +1200 | From | Nigel Cunningham <> | Subject | Re: Software suspend testing in 2.6.0-test1 |
| |
Hi.
In 2.4, I ended up fusing the freezer and shrinking memory together. The essence is:
freeze all other processes while need to free memory unfreeze processes shrink memory until think we have enough freeze processes
Regards,
Nigel
On Sat, 2003-07-19 at 06:04, Pavel Machek wrote: > Hi! > > > > I wanted to avoid that: we do want user threads refrigerated at that > > > point so that we know noone is allocating memory as we are trying to > > > do memory shrink. I'd like to avoid having refrigerator run in two > > > phases.... > > > > But we should be the only process running, and we can guarantee that by > > not sleeping and doing preempt_disable() when we begin. Especially > > if we start the refrigeration sequence after we shrink > > memory. Right? > > If we refrigerate after we shrink, userspace can allocate everything > just after shrink. > Pavel -- Nigel Cunningham 495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless, Christ died for the ungodly. -- Romans 5:6, NIV.
- 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/
| |