Re: what's cooking in zram for 4.1

2015-05-18 Thread Sergey Senozhatsky
On (05/18/15 22:55), Minchan Kim wrote: > > > Why do you need all in one file? ... to provide consistent statistics? > > > > > > > yes, that's the main reason. > > In my side, other main reason was to reduce the number of system call > to see statistics. It is not only syscall overhead itself

Re: what's cooking in zram for 4.1

2015-05-18 Thread Minchan Kim
On Mon, May 18, 2015 at 06:56:49PM +0900, Sergey Senozhatsky wrote: > On (05/18/15 11:36), Karel Zak wrote: > > On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: > > > There will be some user-space visible changes in zram 4.1 we'd love to > > > let you know > > > about. > > > >

Re: what's cooking in zram for 4.1

2015-05-18 Thread Minchan Kim
Hello On Mon, May 11, 2015 at 08:56:02PM +0900, Sergey Senozhatsky wrote: > On (05/11/15 13:38), Karel Zak wrote: > > hmm... frankly, the reason why I love /sys and why hate /proc is > > value-per-file. You do not need special parsers to read from /sys > > (usually). > > > > >

Re: what's cooking in zram for 4.1

2015-05-18 Thread Sergey Senozhatsky
On (05/18/15 11:36), Karel Zak wrote: > On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: > > There will be some user-space visible changes in zram 4.1 we'd love to let > > you know > > about. > > ... > > > -- /sys/block/zram/mm_stat > > > > The stat file represents device's

Re: what's cooking in zram for 4.1

2015-05-18 Thread Karel Zak
On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: > There will be some user-space visible changes in zram 4.1 we'd love to let > you know > about. ... > -- /sys/block/zram/mm_stat > > The stat file represents device's mm statistics. It consists of a single > line of text and

Re: what's cooking in zram for 4.1

2015-05-18 Thread Sergey Senozhatsky
On (05/18/15 22:55), Minchan Kim wrote: Why do you need all in one file? ... to provide consistent statistics? yes, that's the main reason. In my side, other main reason was to reduce the number of system call to see statistics. It is not only syscall overhead itself but also

Re: what's cooking in zram for 4.1

2015-05-18 Thread Minchan Kim
On Mon, May 18, 2015 at 06:56:49PM +0900, Sergey Senozhatsky wrote: On (05/18/15 11:36), Karel Zak wrote: On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: There will be some user-space visible changes in zram 4.1 we'd love to let you know about. ... --

Re: what's cooking in zram for 4.1

2015-05-18 Thread Minchan Kim
Hello On Mon, May 11, 2015 at 08:56:02PM +0900, Sergey Senozhatsky wrote: On (05/11/15 13:38), Karel Zak wrote: hmm... frankly, the reason why I love /sys and why hate /proc is value-per-file. You do not need special parsers to read from /sys (usually). orig_data_size

Re: what's cooking in zram for 4.1

2015-05-18 Thread Karel Zak
On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: There will be some user-space visible changes in zram 4.1 we'd love to let you know about. ... -- /sys/block/zramid/mm_stat The stat file represents device's mm statistics. It consists of a single line of text and

Re: what's cooking in zram for 4.1

2015-05-18 Thread Sergey Senozhatsky
On (05/18/15 11:36), Karel Zak wrote: On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: There will be some user-space visible changes in zram 4.1 we'd love to let you know about. ... -- /sys/block/zramid/mm_stat The stat file represents device's mm statistics.

Re: what's cooking in zram for 4.1

2015-05-11 Thread Sergey Senozhatsky
On (05/11/15 13:38), Karel Zak wrote: > hmm... frankly, the reason why I love /sys and why hate /proc is > value-per-file. You do not need special parsers to read from /sys > (usually). > > > orig_data_size > > compr_data_size > > mem_used_total > > mem_limit > >

Re: what's cooking in zram for 4.1

2015-05-11 Thread Karel Zak
On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: > There will be some user-space visible changes in zram 4.1 we'd love to let > you know > about. Thanks. > 2) zram has deprecated some of the existing stat sysfs attributes. we will > consolidate zramX device's stats in 3

Re: what's cooking in zram for 4.1

2015-05-11 Thread Sergey Senozhatsky
On (05/11/15 13:38), Karel Zak wrote: hmm... frankly, the reason why I love /sys and why hate /proc is value-per-file. You do not need special parsers to read from /sys (usually). orig_data_size compr_data_size mem_used_total mem_limit

Re: what's cooking in zram for 4.1

2015-05-11 Thread Karel Zak
On Sat, May 09, 2015 at 01:21:48PM +0900, Sergey Senozhatsky wrote: There will be some user-space visible changes in zram 4.1 we'd love to let you know about. Thanks. 2) zram has deprecated some of the existing stat sysfs attributes. we will consolidate zramX device's stats in 3 files,

what's cooking in zram for 4.1

2015-05-08 Thread Sergey Senozhatsky
Hello Karel, There will be some user-space visible changes in zram 4.1 we'd love to let you know about. 1) new sysfs node -- /sys/block/zramX/compact triggers zram memory compaction. 2) zram has deprecated some of the existing stat sysfs attributes. we will consolidate zramX device's stats

what's cooking in zram for 4.1

2015-05-08 Thread Sergey Senozhatsky
Hello Karel, There will be some user-space visible changes in zram 4.1 we'd love to let you know about. 1) new sysfs node -- /sys/block/zramX/compact triggers zram memory compaction. 2) zram has deprecated some of the existing stat sysfs attributes. we will consolidate zramX device's stats