On (01/15/14 13:24), Minchan Kim wrote:
> Hello Sergey,
>
> On Tue, Jan 14, 2014 at 12:37:40PM +0300, Sergey Senozhatsky wrote:
> > 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> > `show' functions and reduce code duplication.
> >
> > 2) Account and report back to user
On (01/15/14 13:24), Minchan Kim wrote:
Hello Sergey,
On Tue, Jan 14, 2014 at 12:37:40PM +0300, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of
Hello Sergey,
On Tue, Jan 14, 2014 at 12:37:40PM +0300, Sergey Senozhatsky wrote:
> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> `show' functions and reduce code duplication.
>
> 2) Account and report back to user numbers of failed READ and WRITE
> operations.
>
> 3)
On 01/14/2014 03:09 PM, Sergey Senozhatsky wrote:
> On (01/14/14 15:02), Jerome Marchand wrote:
>> On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
>>> On (01/14/14 14:43), Jerome Marchand wrote:
>>> [..]
>>
>> That's weird: good/bad_compress are accounted, but it seems to me that
>>
On (01/14/14 15:02), Jerome Marchand wrote:
> On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
> > On (01/14/14 14:43), Jerome Marchand wrote:
> > [..]
>
> That's weird: good/bad_compress are accounted, but it seems to me that
> they are to never used in any way. If so, there is
On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
> On (01/14/14 14:43), Jerome Marchand wrote:
> [..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in any way. If so, there is indeed no reason to
keep them.
>
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
> >>
> >> That's weird: good/bad_compress are accounted, but it seems to me that
> >> they are to never used in any way. If so, there is indeed no reason to
> >> keep them.
> >>
> >>
> >>> Account each sub-request
> >>> compression size so we can
On 01/14/2014 12:10 PM, Sergey Senozhatsky wrote:
> On (01/14/14 11:38), Jerome Marchand wrote:
>> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
>>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
>>> `show' functions and reduce code duplication.
>>>
>>> 2) Account and report
On (01/14/14 13:15), Jerome Marchand wrote:
> On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
> >
> > Hello Jerome,
> >
> > On (01/14/14 11:38), Jerome Marchand wrote:
> >> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> >>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
>
> Hello Jerome,
>
> On (01/14/14 11:38), Jerome Marchand wrote:
>> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
>>> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
>>> `show' functions and reduce code duplication.
>>>
>>>
On (01/14/14 11:38), Jerome Marchand wrote:
> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> > 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> > `show' functions and reduce code duplication.
> >
> > 2) Account and report back to user numbers of failed READ and WRITE
> >
Hello Jerome,
On (01/14/14 11:38), Jerome Marchand wrote:
> On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> > 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> > `show' functions and reduce code duplication.
> >
> > 2) Account and report back to user numbers of failed READ
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
> 1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
> `show' functions and reduce code duplication.
>
> 2) Account and report back to user numbers of failed READ and WRITE
> operations.
>
> 3) Remove `good' and `bad' compressed
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
3) Remove `good' and `bad' compressed sub-requests stats. RW request may
cause a number of RW
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
3) Remove `good' and `bad' compressed sub-requests stats. RW request may
cause a number of RW
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
3) Remove `good' and `bad' compressed
Hello Jerome,
On (01/14/14 11:38), Jerome Marchand wrote:
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and
On (01/14/14 11:38), Jerome Marchand wrote:
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
Hello Jerome,
On (01/14/14 11:38), Jerome Marchand wrote:
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and
On (01/14/14 13:15), Jerome Marchand wrote:
On 01/14/2014 11:57 AM, Sergey Senozhatsky wrote:
Hello Jerome,
On (01/14/14 11:38), Jerome Marchand wrote:
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show'
On 01/14/2014 12:10 PM, Sergey Senozhatsky wrote:
On (01/14/14 11:38), Jerome Marchand wrote:
On 01/14/2014 10:37 AM, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in any way. If so, there is indeed no reason to
keep them.
Account each sub-request
compression size so we can calculate real device
On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in any way. If so, there is indeed no reason to
keep them.
Account each sub-request
compression
On (01/14/14 15:02), Jerome Marchand wrote:
On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in any way. If so, there is indeed no reason to
On 01/14/2014 03:09 PM, Sergey Senozhatsky wrote:
On (01/14/14 15:02), Jerome Marchand wrote:
On 01/14/2014 02:53 PM, Sergey Senozhatsky wrote:
On (01/14/14 14:43), Jerome Marchand wrote:
[..]
That's weird: good/bad_compress are accounted, but it seems to me that
they are to never used in
Hello Sergey,
On Tue, Jan 14, 2014 at 12:37:40PM +0300, Sergey Senozhatsky wrote:
1) Introduce ZRAM_ATTR_RO macro to generate zram atomic64_t stats
`show' functions and reduce code duplication.
2) Account and report back to user numbers of failed READ and WRITE
operations.
3) Remove
26 matches
Mail list logo
