Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] Add support for AXFS filesystem type
Date: Wed, 14 Oct 2015 19:06:34 +0200	[thread overview]
Message-ID: <20151014190634.40a649a8@free-electrons.com> (raw)
In-Reply-To: <561E7D5A.1010600@vanguardiasur.com.ar>

Hello,

On Wed, 14 Oct 2015 13:05:46 -0300, Ariel D'Alessandro wrote:

> > You received some feedback on both patches. Could you address this
> > feedback, and submit a new version of the patches?
> 
> Yes, right away.

Excellent, thanks!

> Moreover, "mkfs.axfs tool can receive an additional argument using the
> -i flag which points to a user-created file in the XML format; it
> indicates which pages the user desires to have marked for XIP within the
> file system image." [1]

So probably a Config.in option to specify the path to this file should
be added.

> > I remember there was even a tool to
> > run on the target to "measure" the filesystem accesses, and give some
> > hints on which pages of data should be stored uncompressed vs. which
> > pages should be stored compressed. Is this actually implemented in
> > AXFS ? 
> 
> Yes. The CONFIG_AXFS_PROFILING option is added in order to enable the
> profiling tool. Then simply running on the target platform, the AXFS
> profiler will collect data and write the information it could gather to
> /proc/axfs/volume0. See [1] for more information.

Good. This sort of into can be added in the help text of the Config.in
option.

> > If so, do you plan to add support for such functionality ?
> 
> Yes, it would be nice to add support for this functionality in order to
> explode the entire AXFS capability. I'll do this as a set of follow-up
> patches if that's OK, and let the -a flag (XIP all) for now.

Sounds like a very good plan.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-10-14 17:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 16:55 [Buildroot] [PATCH v2 0/2] Add support for AXFS filesystem type Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 1/2] axfsutils: add new package Ariel D'Alessandro
2015-10-05 18:39   ` Arnout Vandecappelle
2015-10-13 12:06     ` Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 2/2] axfs: add new filesystem type Ariel D'Alessandro
2015-10-05 18:53   ` Arnout Vandecappelle
2015-10-05 18:59     ` Ezequiel Garcia
2015-10-05 19:09       ` Arnout Vandecappelle
2015-10-13 12:12     ` Ariel D'Alessandro
2015-10-13 20:24       ` Yann E. MORIN
2015-10-13 21:14         ` Arnout Vandecappelle
2015-10-13 20:53     ` Yann E. MORIN
2015-10-14 15:50       ` Ariel D'Alessandro
2015-10-13 21:14 ` [Buildroot] [PATCH v2 0/2] Add support for AXFS " Thomas Petazzoni
2015-10-14 16:05   ` Ariel D'Alessandro
2015-10-14 17:06     ` Thomas Petazzoni [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=20151014190634.40a649a8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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