From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8A3B645A2AA for ; Fri, 14 Aug 2026 10:20:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786702814; cv=none; b=PgDw/LpZG/ZAcikqhuW7Affs15vIYB51WZ6so7sPxrWpejIN0nWkdN56+NjQsXvMOSZr/TuupeJJddQOW8jq9NsFgt4f9HnLYGRy6qUegirnLCKly3ayRdQnNDgh6e4mIrBW0QvPXliLLRuUWEETGPP7xRS+8597P5jwJJrdQDE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786702814; c=relaxed/simple; bh=vN1Kd/dc5ytTdio69uh40bSXzxKzVPdmTOx6GQLnxHg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=EWWGfWpQXfs4K7ZIw7FCig3XQ3wItA3Rrftx+r1ryI1aclEWnFStUehhcxGBMFY8mnJS86CJnJjJMIk+KO4SJRsRhcGNcgHWsXvsRcvwCXzKtKqxqWXMaqtQKj8C3rGRn3UUnrSpH1dKz1J50T/yelDU75Y7MlY0V+ia50bAY8g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=4zGtVov0; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=19Bgy5OB; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="4zGtVov0"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="19Bgy5OB" Date: Fri, 14 Aug 2026 12:19:55 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1786702796; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XvtHqPooEuc/u7TjEr4XPu0LgsQ69YSnRmaEaxRUhws=; b=4zGtVov0LQYLDLxfPoU3VoETSJMCEQlPbBniPq2iErscr4pC44YBWsO9o9bjA4VRACCPyF SrOTrRFvg/cFOt7VmOa+pJ2nSGORtlNE3+gHtxs+xuS14M2FN8oEfWFUWIYa9v9Tv13uOg kyubTDRQu/gGq2Arlm1hPGf34TiR6jVbk7inuIeuFvlTlIAyPhtUdnzg3rD6uuwuArN6hF T9Z1DvOq5hb+s+9EsHOkIY211O2qGJOcrrmtyi2BZuL23D8r8PP3Pg6zJ64JE9ioTDqtZ6 JSO4wH/TkvlnmG4hKVMfF/qKh86CcWb1vyi3wclhcvTbxbz6DEyyuBo/eLO78w== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1786702796; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=XvtHqPooEuc/u7TjEr4XPu0LgsQ69YSnRmaEaxRUhws=; b=19Bgy5OBnx6HmGT2MiHKetc7EBCR3TivFBCVAI7MTWGOa8FBFegr1mnBG2xcYt7BGV1IzN sLy8fR1eiIUuuDAw== From: Sebastian Andrzej Siewior To: Sergey Senozhatsky Cc: Barry Song , akpm@linux-foundation.org, hdanton@sina.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, minchan@kernel.org, ryncsn@gmail.com, yosry.ahmed@linux.dev, surenb@google.com, Dongdong Zhang , Suleiman Souhlal Subject: Re: [RFC PATCH] zram: avoid preemption with CPU-based compression backends Message-ID: <20260814101955.71AgFNAt@linutronix.de> References: <20260805005545.66112-1-baohua@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On 2026-08-05 19:25:23 [+0900], Sergey Senozhatsky wrote: > Hi Barry, > > On (26/08/05 15:50), Barry Song wrote: > > BTW, I wonder if compression and decompression could use separate > > mutexes. That way, a sleepable zs_malloc() in the compression path > > would not block decompression, which is the more latency-sensitive > > operation. > > quick and dirty patch. Just curious if this improves anything on your > side. > > We also maybe can have more that num_online_cpus() stream, if we > switch to idle streams list instead [1] > > [1] https://lore.kernel.org/lkml/20250130111105.2861324-3-senozhatsky@chromium.org/ After reading this thread, I got to say that this looks quite nice compared to the other two ;) Sebastian