From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933210AbcLIAgH (ORCPT ); Thu, 8 Dec 2016 19:36:07 -0500 Received: from mail-pf0-f194.google.com ([209.85.192.194]:33724 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932817AbcLIAgG (ORCPT ); Thu, 8 Dec 2016 19:36:06 -0500 Date: Fri, 9 Dec 2016 09:36:11 +0900 From: Sergey Senozhatsky To: Cory Pruce Cc: Nitin Gupta , Sergey Senozhatsky , linux-kernel@vger.kernel.org, minchan@kernel.org Subject: Re: ZRAM struct disk usage Message-ID: <20161209003611.GA4661@jagdpanzerIV.localdomain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (12/08/16 11:17), Cory Pruce wrote: > Just wondering if it was really necessary to use the disk struct. It seems > like the struct is more used for record keeping/io config than actually > holding the data (actual data is worked with via page operations). > > Is this correct? What was the main need to use the data structure? I see > that the one and only partition is used for io acct but this seems more > nice to have to me than truly necessary being that this isn't an actual > peripheral. because we want to have an actual block device with disk capacity, device IO request queue and so no. -ss