Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752729AbZIYVgV (ORCPT ); Fri, 25 Sep 2009 17:36:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752360AbZIYVgV (ORCPT ); Fri, 25 Sep 2009 17:36:21 -0400 Received: from 8bytes.org ([88.198.83.132]:58112 "EHLO 8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751803AbZIYVgU (ORCPT ); Fri, 25 Sep 2009 17:36:20 -0400 X-Greylist: delayed 1601 seconds by postgrey-1.27 at vger.kernel.org; Fri, 25 Sep 2009 17:36:20 EDT Date: Fri, 25 Sep 2009 23:09:42 +0200 From: Joerg Roedel To: Nigel Cunningham Cc: KAMEZAWA Hiroyuki , LKML , "linux-mm@kvack.org" Subject: Re: No more bits in vm_area_struct's vm_flags. Message-ID: <20090925210942.GB29634@8bytes.org> References: <4AB9A0D6.1090004@crca.org.au> <20090924100518.78df6b93.kamezawa.hiroyu@jp.fujitsu.com> <4ABC80B0.5010100@crca.org.au> <20090925174009.79778649.kamezawa.hiroyu@jp.fujitsu.com> <4ABC83E2.7050300@crca.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ABC83E2.7050300@crca.org.au> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1346 Lines: 33 On Fri, Sep 25, 2009 at 06:48:34PM +1000, Nigel Cunningham wrote: > Hi. > > KAMEZAWA Hiroyuki wrote: > > On Fri, 25 Sep 2009 18:34:56 +1000 > > Nigel Cunningham wrote: > > > >> Hi. > >> > >> KAMEZAWA Hiroyuki wrote: > >>>> I have some code in TuxOnIce that needs a bit too (explicitly mark the > >>>> VMA as needing to be atomically copied, for GEM objects), and am not > >>>> sure what the canonical way to proceed is. Should a new unsigned long be > >>>> added? The difficulty I see with that is that my flag was used in > >>>> shmem_file_setup's flags parameter (drm_gem_object_alloc), so that > >>>> function would need an extra parameter too.. > >>> Hmm, how about adding vma->vm_flags2 ? > >> The difficulty there is that some functions pass these flags as arguments. > >> > > Ah yes. But I wonder some special flags, which is rarey used, can be moved > > to vm_flags2... But please don't call it vm_flags2. I think its better to partition the existing flags by there purpose somehow hand give the flags fields appropriate names which express that purpose. Joerg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/