Hey Sergey, On Mon, Aug 25, 2014 at 08:09:27PM +0900, Sergey Senozhatsky wrote: > On (08/25/14 09:05), Minchan Kim wrote: > > Since zram has no control feature to limit memory usage, > > it makes hard to manage system memrory. > > > > This patch adds new knob "mem_limit" via sysfs to set up the > > a limit so that zram could fail allocation once it reaches > > the limit. > > > > In addition, user could change the limit in runtime so that > > he could manage the memory more dynamically. > > > > Initial state is no limit so it doesn't break old behavior. > > > > Signed-off-by: Minchan Kim <minc...@kernel.org> > > --- > > Documentation/ABI/testing/sysfs-block-zram | 10 ++++++++ > > Documentation/blockdev/zram.txt | 24 ++++++++++++++--- > > drivers/block/zram/zram_drv.c | 41 > > ++++++++++++++++++++++++++++++ > > drivers/block/zram/zram_drv.h | 5 ++++ > > 4 files changed, 76 insertions(+), 4 deletions(-) > > > > diff --git a/Documentation/ABI/testing/sysfs-block-zram > > b/Documentation/ABI/testing/sysfs-block-zram > > index 70ec992514d0..dbe643775ec1 100644 > > --- a/Documentation/ABI/testing/sysfs-block-zram > > +++ b/Documentation/ABI/testing/sysfs-block-zram > > @@ -119,3 +119,13 @@ Description: > > efficiency can be calculated using compr_data_size and this > > statistic. > > Unit: bytes > > + > > +What: /sys/block/zram<id>/mem_limit > > +Date: August 2014 > > +Contact: Minchan Kim <minc...@kernel.org> > > +Description: > > + The mem_limit file is read/write and specifies the amount > > + of memory to be able to consume memory to store store > > + compressed data. The limit could be changed in run time > > + and "0" means disable the limit. No limit is the initial state. > > just a nitpick, sorry. > "the amount of memory to be able to consume memory to store store compressed > data" > ^^^^^^^ > > "the maximum amount of memory ZRAM can use to store the compressed data"?
Will fix. Thanks. -- Kind regards, Minchan Kim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
