From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754154AbbCEBdO (ORCPT ); Wed, 4 Mar 2015 20:33:14 -0500 Received: from mail-pa0-f46.google.com ([209.85.220.46]:41900 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753739AbbCEBdL (ORCPT ); Wed, 4 Mar 2015 20:33:11 -0500 Date: Thu, 5 Mar 2015 10:33:02 +0900 From: Minchan Kim To: Sergey Senozhatsky Cc: Andrew Morton , Sergey Senozhatsky , Nitin Gupta , linux-kernel@vger.kernel.org, Jerome Marchand Subject: Re: [PATCH 0/2] make automatic device_id generation possible Message-ID: <20150305013301.GA5041@blaptop> References: <1425478601-19141-1-git-send-email-sergey.senozhatsky@gmail.com> <20150305001954.GA9563@blaptop> <20150305005829.GC14927@swordfish> <20150305012043.GD14927@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150305012043.GD14927@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 Thu, Mar 05, 2015 at 10:20:43AM +0900, Sergey Senozhatsky wrote: > 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. They upgraded the system and from now on, one of app tries automatic id with zram for some reason. What happens if he gets some user id before the user login? The system should have fallback in the case of failing to create own userid assignment. Hmm, Coexisting specific and automatic id assign seem to be not a godd idea. > > -ss -- Kind regards, Minchan Kim