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: Tue, 13 Oct 2015 23:14:28 +0200 [thread overview]
Message-ID: <20151013231428.2e611e06@free-electrons.com> (raw)
In-Reply-To: <1444064102-13575-1-git-send-email-ariel@vanguardiasur.com.ar>
Dear Ariel D'Alessandro,
On Mon, 5 Oct 2015 13:55:00 -0300, Ariel D'Alessandro wrote:
> This patch series adds support for using the AXFS filesystem type.
>
> The Advanced XIP File System is a Linux kernel filesystem driver that enables
> files to be executed directly from flash or ROM memory rather than being copied
> into RAM.
>
> More info can be found here: http://elinux.org/AXFS
>
> Changes from v1:
> * Removed unnecessary call to $(generic-package) in axfsutils.mk.
>
> Ariel
>
> Ariel D'Alessandro (2):
> axfsutils: add new package
> axfs: add new filesystem type
You received some feedback on both patches. Could you address this
feedback, and submit a new version of the patches?
Note that adding the axfs patches as a kernel extension, as suggested
by Yann E. Morin, is optional and can perfectly be done as a set of
follow-up patches: it is not mandatory to have this part of the current
series.
However, one thing that I remember about AXFS is that you could decide
when creating the root filesystem, which parts of which files would be
stored uncompressed (so that they can be XIP-ed) and which parts of
which files would be stored compressed (to save space). This allowed to
combine the nice aspects of a XIP-capable filesystem, with the nice
aspects of a compressed filesystem. 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 ? If so, do you plan to add support for such functionality ?
In any case, I'll mark your patches as "Changes Requested" in
patchwork, so please resubmit a new version when you have time,
otherwise we'll forget about your contribution.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-13 21:14 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 ` Thomas Petazzoni [this message]
2015-10-14 16:05 ` [Buildroot] [PATCH v2 0/2] Add support for AXFS " Ariel D'Alessandro
2015-10-14 17:06 ` Thomas Petazzoni
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=20151013231428.2e611e06@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