[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <466A2D4F.3040300@us.ibm.com>
Date: Fri, 08 Jun 2007 21:32:15 -0700
From: Badari Pulavarty <pbadari@...ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Albert Cahalan <acahalan@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
torvalds@...ux-foundation.org
Subject: Re: [PATCH] shm: Fix the filename of hugetlb sysv shared memory
Andrew Morton wrote:
>On Fri, 08 Jun 2007 17:43:34 -0600
>ebiederm@...ssion.com (Eric W. Biederman) wrote:
>
>>Some user space tools need to identify SYSV shared memory when
>>examining /proc/<pid>/maps. To do so they look for a block device
>>with major zero, a dentry named SYSV<sysv key>, and having the minor of
>>the internal sysv shared memory kernel mount.
>>
>>To help these tools and to make it easier for people just browsing
>>/proc/<pid>/maps this patch modifies hugetlb sysv shared memory to
>>use the SYSV<key> dentry naming convention.
>>
>>User space tools will still have to be aware that hugetlb sysv
>>shared memory lives on a different internal kernel mount and so
>>has a different block device minor number from the rest of sysv
>>shared memory.
>>
>
>I assume this fix is preferred over Badari's? If so, why?
>
No. You still need my patch to fix the current breakage.
This patch makes hugetlbfs also use same naming convention as regular
shmem for its
name. This is not absolutely needed, its a nice to have. Currently, user
space tools
can't depend on the filename alone, since its not unique (based on kry).
Thanks,
Badari
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists