public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Richard Chang <richardycc@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/3] zram: optimal post-processing target selection
Date: Sun, 8 Sep 2024 20:47:24 +0900	[thread overview]
Message-ID: <20240908114724.GC2413563@google.com> (raw)
In-Reply-To: <20240908114507.GB2413563@google.com>

On (24/09/08 20:45), Sergey Senozhatsky wrote:
> On (24/09/08 20:42), Sergey Senozhatsky wrote:
> > 
> > v2..v1:
> > -- clear PP_SLOT when slot is accessed
> > -- kmalloc pp_ctl instead of keeoing it on the stack
> > -- increase the number of pp-buckets and rework the way it's defined
> > -- code reshuffle and refactoring
> >
>
> D'oh... Let me re-send it properly.  It was supposed to be sent to
> Minchan and Andrew.  Sorry for the noise.

Re-sent under the same name
https://lore.kernel.org/lkml/20240908114541.3025351-1-senozhatsky@chromium.org/

  reply	other threads:[~2024-09-08 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-08 11:42 [PATCHv2 0/3] zram: optimal post-processing target selection Sergey Senozhatsky
2024-09-08 11:42 ` [PATCHv2 1/3] zram: introduce ZRAM_PP_SLOT flag Sergey Senozhatsky
2024-09-08 11:42 ` [PATCHv2 2/3] zram: rework recompress target selection strategy Sergey Senozhatsky
2024-09-08 11:42 ` [PATCHv2 3/3] zram: rework writeback " Sergey Senozhatsky
2024-09-08 11:45 ` [PATCHv2 0/3] zram: optimal post-processing target selection Sergey Senozhatsky
2024-09-08 11:47   ` Sergey Senozhatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-08 11:45 Sergey Senozhatsky
2024-09-10  9:37 ` Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240908114724.GC2413563@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardycc@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox