linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: "Gioh Kim" <gioh.kim@lge.com>, "Theodore Ts'o" <tytso@mit.edu>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Andreas Dilger" <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org, "Minchan Kim" <minchan@kernel.org>,
	"Joonsoo Kim" <js1304@gmail.com>, 이건호 <gunho.lee@lge.com>
Subject: Re: [PATCH 0/2] new APIs to allocate buffer-cache for superblock in non-movable area
Date: Thu, 21 Aug 2014 14:38:00 -0700	[thread overview]
Message-ID: <20140821143800.8eef83c98bffbeb700830edf@linux-foundation.org> (raw)
In-Reply-To: <20140818121146.GD9603@quack.suse.cz>

On Mon, 18 Aug 2014 14:11:46 +0200 Jan Kara <jack@suse.cz> wrote:

> > >Yes, but are you actually *using* the ext4 partitions for anything?
> > >If this is a realistic real world use case, file systems are used to
> > >store, well, files, and that means there will be inodes and dentry
> > >cache entries that will also be allocated.  Does your test scenario
> > >reflect real world usage?
> > 
> > Yes. I'm working for LG Electronics.
> > My test platform is currently selling item in the market.
> > And also I test my patch when my platform is working as if real user uses it.
>   Great, this is exactly what I was looking for. So if it really makes
> your usecase work I don't have objections to your solution (after you
> change what Andrew suggested).

Yup.  This sort os real-world usage information is terribly important
and the more you can tell us the better.  It helps us all to allocate
our time to the places where it is most needed...

      reply	other threads:[~2014-08-21 21:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14  5:12 [PATCH 0/2] new APIs to allocate buffer-cache for superblock in non-movable area Gioh Kim
2014-08-14  5:15 ` [PATCH 1/2] fs/buffer.c: allocate buffer cache from " Gioh Kim
2014-08-14  5:19   ` Gioh Kim
2014-08-14 21:22   ` Andrew Morton
2014-08-18  1:19     ` Gioh Kim
2014-08-14  5:16 ` [PATCH 2/3] ext4: allocate buffer-cache for superblock in, " Gioh Kim
2014-08-14  5:17 ` [PATCH 3/3] jbd/jbd2: allocate buffer-cache for superblock inode " Gioh Kim
2014-08-14  5:19 ` [PATCH 0/2] new APIs to allocate buffer-cache for superblock in " Gioh Kim
2014-08-14  5:23 ` Gioh Kim
2014-08-14 21:26 ` Andrew Morton
2014-08-16 18:52   ` Jan Kara
2014-08-18  1:15     ` Gioh Kim
2014-08-18  3:24       ` Theodore Ts'o
2014-08-18  4:44         ` Gioh Kim
2014-08-18 12:11           ` Jan Kara
2014-08-21 21:38             ` Andrew Morton [this message]

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=20140821143800.8eef83c98bffbeb700830edf@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=gioh.kim@lge.com \
    --cc=gunho.lee@lge.com \
    --cc=jack@suse.cz \
    --cc=js1304@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).