From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from out-180.mta1.migadu.com (out-180.mta1.migadu.com [95.215.58.180])
	(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 3C9271CDFD5
	for <linux-kernel@vger.kernel.org>; Tue, 28 Jan 2025 17:22:36 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.180
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1738084958; cv=none; b=s39pbHFvX3kpRBMZKgvlPjFDzWkHgvzSF3LyykngCDyWjkEADU26ybYUJT/D5QprxZDb85Tj+HCh4SsDSAd5JMxTSmfad4KK8JBsHeXqx2pMYOnQcbE2UBlkd7xnLQQ9MCz+0OvmYXlZ5uYlM2PncZ20k/UsSyIH8ZDAB1hu0JI=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1738084958; c=relaxed/simple;
	bh=K5sTZf5Pz4hIKWeotFPgBVF1nPSX2bvdQakNVeO6Hy0=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=ij3/EYobXiV7rZKj3fT9t3IZwodPha6CmGj+m/oFnKqCpcd0X/j0mN9YflzdmDD3uRWYND9KU8jUbkMGRglbrIM/IqRwvJd+sdYowfXv0YlDs8KhSLd5ktB8aOPLV+aSuz2DYp9nTD1zljVOsZF+HUkbBbt52jjM2lAQpgF6BHY=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=EIR/8nL/; arc=none smtp.client-ip=95.215.58.180
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="EIR/8nL/"
Date: Tue, 28 Jan 2025 17:22:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1;
	t=1738084954;
	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=1LErTtuCZH9L/hiJGEo1GHjacbTv+fpaWirNj7UCFhU=;
	b=EIR/8nL/ZQ8GyjzImRhru+Nug/bu4Nbhoqpk8oQ+JXxyRIs40l/nHzFSj8AVYCj7eAnSyo
	swEgoWdcX7xd2KdcfDX7cn0RC6Ftw2rKBxrpKxUpJPLF7HUTGHEgMP2yyzrocCxxcUagAC
	vr/8lLDIfcPAewyEn+S6mXkajK0hebg=
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Yosry Ahmed <yosry.ahmed@linux.dev>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>, Nhat Pham <nphamcs@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 5/6] zsmalloc: introduce handle mapping API
Message-ID: <Z5kSVqFs4I1RBmwx@google.com>
References: <20250127080254.1302026-1-senozhatsky@chromium.org>
 <20250127080254.1302026-6-senozhatsky@chromium.org>
 <Z5gBdvLmsPAHKyZt@google.com>
 <ajg3gij4v2kzdmgpy3qjutfxsispuxjqkj7u7digdjqi5pst5i@3v2g2lra3ay3>
 <Z5g0gITP8psSdqwj@google.com>
 <m7xv5v46sowhm7xwutv5zqxpfygcg2r3asfd3npakmacap6wq2@prtxaiwzzgjn>
 <5nhnrq753euz3exuirvkpvq5ycrpik7er6mgpu66zp2emt5xf4@7n2vzbghlzmd>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5nhnrq753euz3exuirvkpvq5ycrpik7er6mgpu66zp2emt5xf4@7n2vzbghlzmd>
X-Migadu-Flow: FLOW_OUT

On Tue, Jan 28, 2025 at 08:10:10PM +0900, Sergey Senozhatsky wrote:
> On (25/01/28 14:29), Sergey Senozhatsky wrote:
> > Maybe we can teach compaction and migration to try-WRITE and
> > bail out if the page is locked, but I don't know.
> 
> This seems to be working just fine.

Does this mean we won't need as much locking changes to get zsmalloc to
be preemtible?

I am slightly worried about how these changes will affect performance
tbh.