Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A1BBC433FE for ; Tue, 4 Jan 2022 14:46:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234379AbiADOqr (ORCPT ); Tue, 4 Jan 2022 09:46:47 -0500 Received: from verein.lst.de ([213.95.11.211]:50184 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232977AbiADOqr (ORCPT ); Tue, 4 Jan 2022 09:46:47 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 0E84468AFE; Tue, 4 Jan 2022 15:46:43 +0100 (CET) Date: Tue, 4 Jan 2022 15:46:42 +0100 From: Christoph Hellwig To: David Hildenbrand Cc: Christoph Hellwig , Andrew Morton , Konrad Rzeszutek Wilk , Hugh Dickins , Seth Jennings , Dan Streetman , Vitaly Wool , Matthew Wilcox , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Subject: Re: remove Xen tmem leftovers Message-ID: <20220104144642.GA23411@lst.de> References: <20211224062246.1258487-1-hch@lst.de> <10ec73d4-6658-4f60-abe1-84ece53ca373@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10ec73d4-6658-4f60-abe1-84ece53ca373@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 04, 2022 at 03:31:20PM +0100, David Hildenbrand wrote: > Just out of curiosity, why was tmem removed from Linux (or even Xen?). > Do you have any information? "The Xen tmem (transcendent memory) driver can be removed, as the related Xen hypervisor feature never made it past the "experimental" state and will be removed in future Xen versions (>= 4.13). The xen-selfballoon driver depends on tmem, so it can be removed, too."