Messages in this thread | | | Subject | Re: [-mm PATCH] Memory controller improve user interface (v3) | From | Dave Hansen <> | Date | Tue, 04 Sep 2007 12:03:13 -0700 |
| |
On Sun, 2007-09-02 at 16:20 +0530, Balbir Singh wrote: > > +Setting a limit to a number that is not a multiple of page size causes > +rounding up of the value. The user must check back to see (by reading > +memory.limit_in_bytes), to check for differences between desired values and > +committed values. Currently, all accounting is done in multiples of PAGE_SIZE
I wonder if we can say this in a bit more generic fashion.
A successful write to this file does not guarantee a successful set of this limit to the value written into the file. This can be due to a number of factors, such as rounding up to page boundaries or the total availability of memory on the system. The user is required to re-read this file after a write to guarantee the value committed by the kernel.
This keeps a user from saying "I page aligned the value I stuck in there, no I don't have to check it."
-- Dave
- 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/
| |