All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gioh Kim <gi-oh.kim@profitbricks.com>
To: Al Viro <viro@ZenIV.linux.org.uk>, Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	jlayton@poochiereds.net, bfields@fieldses.org,
	Vlastimil Babka <vbabka@suse.cz>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	koct9i@gmail.com, aquini@redhat.com,
	virtualization@lists.linux-foundation.org,
	Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	rknize@motorola.com, Rik van Riel <riel@redhat.com>,
	Gioh Kim <gurugio@hanmail.net>
Subject: Re: [PATCH v1 03/19] fs/anon_inodes: new interface to create new inode
Date: Fri, 11 Mar 2016 15:24:36 +0100	[thread overview]
Message-ID: <56E2D524.8070708@profitbricks.com> (raw)
In-Reply-To: <20160311080503.GR17997@ZenIV.linux.org.uk>



On 11.03.2016 09:05, Al Viro wrote:
> On Fri, Mar 11, 2016 at 04:30:07PM +0900, Minchan Kim wrote:
>> From: Gioh Kim <gurugio@hanmail.net>
>>
>> The anon_inodes has already complete interfaces to create manage
>> many anonymous inodes but don't have interface to get
>> new inode. Other sub-modules can create anonymous inode
>> without creating and mounting it's own pseudo filesystem.
> IMO that's a bad idea.  In case of aio "creating and mounting" takes this:
> static struct dentry *aio_mount(struct file_system_type *fs_type,
>                                  int flags, const char *dev_name, void *data)
> {
>          static const struct dentry_operations ops = {
>                  .d_dname        = simple_dname,
>          };
>          return mount_pseudo(fs_type, "aio:", NULL, &ops, AIO_RING_MAGIC);
> }
> and
>          static struct file_system_type aio_fs = {
>                  .name           = "aio",
>                  .mount          = aio_mount,
>                  .kill_sb        = kill_anon_super,
>          };
>          aio_mnt = kern_mount(&aio_fs);
>
> All of 12 lines.  Your export is not much shorter.  To quote old mail on
> the same topic:
I know what aio_setup() does. It can be a solution.
But I thought creating anon_inode_new() is simpler than several drivers 
create its own pseudo filesystem.
Creating a filesystem requires memory allocation and locking some lists 
even though it is pseudo.

Could you inform me if there is a reason we should avoid creating 
anonymous inode?

>
>> Note that anon_inodes.c reason to exist was "it's for situations where
>> all context lives on struct file and we don't need separate inode for
>> them".  Going from that to "it happens to contain a handy function for inode
>> allocation"...


-- 
Best regards,
Gioh Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Gioh Kim <gi-oh.kim@profitbricks.com>
To: Al Viro <viro@ZenIV.linux.org.uk>, Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	jlayton@poochiereds.net, bfields@fieldses.org,
	Vlastimil Babka <vbabka@suse.cz>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	koct9i@gmail.com, aquini@redhat.com,
	virtualization@lists.linux-foundation.org,
	Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	rknize@motorola.com, Rik van Riel <riel@redhat.com>,
	Gioh Kim <gurugio@hanmail.net>
Subject: Re: [PATCH v1 03/19] fs/anon_inodes: new interface to create new inode
Date: Fri, 11 Mar 2016 15:24:36 +0100	[thread overview]
Message-ID: <56E2D524.8070708@profitbricks.com> (raw)
In-Reply-To: <20160311080503.GR17997@ZenIV.linux.org.uk>



On 11.03.2016 09:05, Al Viro wrote:
> On Fri, Mar 11, 2016 at 04:30:07PM +0900, Minchan Kim wrote:
>> From: Gioh Kim <gurugio@hanmail.net>
>>
>> The anon_inodes has already complete interfaces to create manage
>> many anonymous inodes but don't have interface to get
>> new inode. Other sub-modules can create anonymous inode
>> without creating and mounting it's own pseudo filesystem.
> IMO that's a bad idea.  In case of aio "creating and mounting" takes this:
> static struct dentry *aio_mount(struct file_system_type *fs_type,
>                                  int flags, const char *dev_name, void *data)
> {
>          static const struct dentry_operations ops = {
>                  .d_dname        = simple_dname,
>          };
>          return mount_pseudo(fs_type, "aio:", NULL, &ops, AIO_RING_MAGIC);
> }
> and
>          static struct file_system_type aio_fs = {
>                  .name           = "aio",
>                  .mount          = aio_mount,
>                  .kill_sb        = kill_anon_super,
>          };
>          aio_mnt = kern_mount(&aio_fs);
>
> All of 12 lines.  Your export is not much shorter.  To quote old mail on
> the same topic:
I know what aio_setup() does. It can be a solution.
But I thought creating anon_inode_new() is simpler than several drivers 
create its own pseudo filesystem.
Creating a filesystem requires memory allocation and locking some lists 
even though it is pseudo.

Could you inform me if there is a reason we should avoid creating 
anonymous inode?

>
>> Note that anon_inodes.c reason to exist was "it's for situations where
>> all context lives on struct file and we don't need separate inode for
>> them".  Going from that to "it happens to contain a handy function for inode
>> allocation"...


-- 
Best regards,
Gioh Kim

  reply	other threads:[~2016-03-11 14:24 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  7:30 [PATCH v1 00/19] Support non-lru page migration Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 01/19] mm: use put_page to free page instead of putback_lru_page Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-14  8:48   ` Vlastimil Babka
2016-03-14  8:48     ` Vlastimil Babka
2016-03-15  1:16     ` Minchan Kim
2016-03-15  1:16       ` Minchan Kim
2016-03-15  1:16       ` Minchan Kim
2016-03-15 19:06       ` Vlastimil Babka
2016-03-15 19:06       ` Vlastimil Babka
2016-03-15 19:06         ` Vlastimil Babka
2016-03-14  8:48   ` Vlastimil Babka
2016-03-11  7:30 ` [PATCH v1 02/19] mm/compaction: support non-lru movable page migration Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  8:11   ` kbuild test robot
2016-03-11  8:11   ` kbuild test robot
2016-03-11  8:11     ` kbuild test robot
2016-03-11  8:11     ` kbuild test robot
2016-03-11  8:35     ` Minchan Kim
2016-03-11  8:35       ` Minchan Kim
2016-03-11  8:35     ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 03/19] fs/anon_inodes: new interface to create new inode Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  8:05   ` Al Viro
2016-03-11  8:05     ` Al Viro
2016-03-11 14:24     ` Gioh Kim [this message]
2016-03-11 14:24       ` Gioh Kim
2016-03-11 14:24     ` Gioh Kim
2016-03-11  8:05   ` Al Viro
2016-03-11  7:30 ` [PATCH v1 04/19] mm/balloon: use general movable page feature into balloon Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 05/19] zsmalloc: use first_page rather than page Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:19   ` Sergey Senozhatsky
2016-03-15  6:19     ` Sergey Senozhatsky
2016-03-15  6:19   ` Sergey Senozhatsky
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 06/19] zsmalloc: clean up many BUG_ON Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:19   ` Sergey Senozhatsky
2016-03-15  6:19     ` Sergey Senozhatsky
2016-03-15  6:19   ` Sergey Senozhatsky
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 07/19] zsmalloc: reordering function parameter Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:20   ` Sergey Senozhatsky
2016-03-15  6:20     ` Sergey Senozhatsky
2016-03-15  6:20   ` Sergey Senozhatsky
2016-03-11  7:30 ` [PATCH v1 08/19] zsmalloc: remove unused pool param in obj_free Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:21   ` Sergey Senozhatsky
2016-03-15  6:21     ` Sergey Senozhatsky
2016-03-15  6:21   ` Sergey Senozhatsky
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 09/19] zsmalloc: keep max_object in size_class Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-12  1:44   ` xuyiping
2016-03-12  1:44     ` xuyiping
2016-03-14  4:55     ` Minchan Kim
2016-03-14  4:55       ` Minchan Kim
2016-03-14  4:55       ` Minchan Kim
2016-03-12  1:44   ` xuyiping
2016-03-15  6:28   ` Sergey Senozhatsky
2016-03-15  6:28   ` Sergey Senozhatsky
2016-03-15  6:28     ` Sergey Senozhatsky
2016-03-15  6:41     ` Minchan Kim
2016-03-15  6:41       ` Minchan Kim
2016-03-15  6:41     ` Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 10/19] zsmalloc: squeeze inuse into page->mapping Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 11/19] zsmalloc: squeeze freelist " Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:40   ` Sergey Senozhatsky
2016-03-15  6:40   ` Sergey Senozhatsky
2016-03-15  6:40     ` Sergey Senozhatsky
2016-03-15  6:51     ` Minchan Kim
2016-03-15  6:51       ` Minchan Kim
2016-03-17 12:09       ` YiPing Xu
2016-03-17 12:09         ` YiPing Xu
2016-03-17 22:17         ` Minchan Kim
2016-03-17 22:17           ` Minchan Kim
2016-03-17 22:17           ` Minchan Kim
2016-03-17 12:09       ` YiPing Xu
2016-03-15  6:51     ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 12/19] zsmalloc: move struct zs_meta from mapping to freelist Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 13/19] zsmalloc: factor page chain functionality out Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-12  3:09   ` xuyiping
2016-03-12  3:09   ` xuyiping
2016-03-12  3:09     ` xuyiping
2016-03-14  4:58     ` Minchan Kim
2016-03-14  4:58       ` Minchan Kim
2016-03-14  4:58       ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 14/19] zsmalloc: separate free_zspage from putback_zspage Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 15/19] zsmalloc: zs_compact refactoring Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 16/19] zsmalloc: migrate head page of zspage Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 17/19] zsmalloc: use single linked list for page chain Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 18/19] zsmalloc: migrate tail pages in zspage Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-11  7:30 ` [PATCH v1 19/19] zram: use __GFP_MOVABLE for memory allocation Minchan Kim
2016-03-11  7:30 ` Minchan Kim
2016-03-11  7:30   ` Minchan Kim
2016-03-15  6:56   ` Sergey Senozhatsky
2016-03-15  6:56   ` Sergey Senozhatsky
2016-03-15  6:56     ` Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E2D524.8070708@profitbricks.com \
    --to=gi-oh.kim@profitbricks.com \
    --cc=akpm@linux-foundation.org \
    --cc=aquini@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=gurugio@hanmail.net \
    --cc=hughd@google.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jlayton@poochiereds.net \
    --cc=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    --cc=rknize@motorola.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.