linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	gthelen@google.com, m-ikeda@ds.jp.nec.com,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 1/7][memcg] virtually indexed array library.
Date: Wed, 28 Jul 2010 09:08:54 +0900	[thread overview]
Message-ID: <20100728090854.9b255f7c.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100727122949.3bfbfd0a@bike.lwn.net>

On Tue, 27 Jul 2010 12:29:49 -0600
Jonathan Corbet <corbet@lwn.net> wrote:

> On Tue, 27 Jul 2010 16:53:03 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> 
> > This virt-array allocates a virtally contiguous array via get_vm_area()
> > and allows object allocation per an element of array.
> 
> Quick question: this looks a lot like the "flexible array" mechanism
> which went in around a year ago, and which is documented in
> Documentation/flexible-arrays.txt.  I'm not sure we need two of
> these...  That said, it appears that there are still no users of
> flexible arrays.  If your virtually-indexed arrays provide something
> that flexible arrays don't, perhaps your implementation should replace
> flexible arrays?

Hmm. As Documentatin/flexible-arrays.txt says,

"The down sides are that the arrays cannot be indexed directly, individual object
 size cannot exceed the system page size, and putting data into a flexible array
 requires a copy operation. "

This virtually-indexed array is

 - the arrays can be indexed directly.
 - individual object size can be defined arbitrary.
 - puttind data into virt-array requires memory allocation via alloc_varray_item().

But, virtyally-indexed array has its own down side, too.

 - It uses vmalloc() area. This can be very limited in 32bit archs.
 - It cannot be used in !MMU archs.
 - It may consume much TLBs because vmalloc area tends not to be backed by hugepage.

Especially, I think !MMU case is much different. So, there are functional
difference. I implemented this to do quick direct access to objects by indexes.
Otherwise, flex-array may be able to provide more generic frameworks.

Then, I myself don't think virt-array is a replacemento for flex-array.

A discussion "flex-array should be dropped or not" is out of my scope, sorry.
I think you can ask to drop it just because it's almost dead without mentioning
virt-array.

Thanks,
-Kame
 


--
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>

  reply	other threads:[~2010-07-28  0:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  7:51 [RFC][PATCH 0/7][memcg] towards I/O aware memory cgroup KAMEZAWA Hiroyuki
2010-07-27  7:53 ` [RFC][PATCH 1/7][memcg] virtually indexed array library KAMEZAWA Hiroyuki
2010-07-27 18:29   ` Jonathan Corbet
2010-07-28  0:08     ` KAMEZAWA Hiroyuki [this message]
2010-07-28 19:45   ` Andrew Morton
2010-07-29  0:32     ` KAMEZAWA Hiroyuki
2010-07-29  4:27       ` KAMEZAWA Hiroyuki
2010-08-02 18:00         ` Balbir Singh
2010-08-02 23:45           ` KAMEZAWA Hiroyuki
2010-07-27  7:54 ` [RFC][PATCH 2/7][memcg] cgroup arbitarary ID allocation KAMEZAWA Hiroyuki
2010-07-28  2:30   ` Vivek Goyal
2010-07-28  2:35     ` KAMEZAWA Hiroyuki
2010-07-28  3:10       ` Vivek Goyal
2010-08-02 18:04   ` Balbir Singh
2010-08-02 23:45     ` KAMEZAWA Hiroyuki
2010-07-27  7:55 ` [RFC][PATCH 3/7][memcg] memcg on virt array for quick access via ID KAMEZAWA Hiroyuki
2010-07-27  7:56 ` [RFC][PATCH 4/7][memcg] memcg use ID in page_cgroup KAMEZAWA Hiroyuki
2010-07-28  2:39   ` Vivek Goyal
2010-07-28  2:44     ` KAMEZAWA Hiroyuki
2010-07-28  3:13       ` Vivek Goyal
2010-07-28  3:18         ` KAMEZAWA Hiroyuki
2010-07-28  3:21           ` KAMEZAWA Hiroyuki
2010-07-28 14:17             ` Vivek Goyal
2010-07-28 15:43         ` Munehiro Ikeda
2010-07-27  7:59 ` [RFC][PATCH 5/7][memcg] memcg lockless update of file mapped KAMEZAWA Hiroyuki
2010-07-28  7:09   ` Greg Thelen
2010-07-28  7:13     ` KAMEZAWA Hiroyuki
2010-07-27  8:00 ` [RFC][PATCH 6/7][memcg] generic file status update KAMEZAWA Hiroyuki
2010-07-28  7:12   ` Greg Thelen
2010-07-28  7:14     ` KAMEZAWA Hiroyuki
2010-07-27  8:02 ` [RFC][PATCH 7/7][memcg] use spin lock instead of bit_spin_lock in page_cgroup KAMEZAWA Hiroyuki
2010-07-28  6:16   ` Greg Thelen
2010-07-28  6:20     ` KAMEZAWA Hiroyuki
2010-08-02 18:09     ` Balbir Singh
2010-08-02 23:46       ` KAMEZAWA Hiroyuki
2010-07-28  0:13 ` [RFC][PATCH 0/7][memcg] towards I/O aware memory cgroup KAMEZAWA Hiroyuki
2010-07-28 14:42 ` Balbir Singh

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=20100728090854.9b255f7c.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=gthelen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox