From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753730AbbCEBUk (ORCPT ); Wed, 4 Mar 2015 20:20:40 -0500 Received: from mail-pa0-f51.google.com ([209.85.220.51]:42396 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752533AbbCEBUi (ORCPT ); Wed, 4 Mar 2015 20:20:38 -0500 Date: Thu, 5 Mar 2015 10:20:43 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Andrew Morton , Sergey Senozhatsky , Sergey Senozhatsky , Nitin Gupta , linux-kernel@vger.kernel.org, Jerome Marchand Subject: Re: [PATCH 0/2] make automatic device_id generation possible Message-ID: <20150305012043.GD14927@swordfish> References: <1425478601-19141-1-git-send-email-sergey.senozhatsky@gmail.com> <20150305001954.GA9563@blaptop> <20150305005829.GC14927@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150305005829.GC14927@swordfish> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (03/05/15 09:58), Sergey Senozhatsky wrote: > /* yet "/dev/zram$(id -u)" thing looks interesting */ > hm, I can think of a huge build server with tons of users. /dev/zram$(id -u) created during user login and destroyed during logout. so users use theirs own zram devices with predictable device ids (which also makes it simpler for admin) for compilation/etc., and don't pressure hdds that much. -ss