From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] jfs: neatening
Date: Wed, 5 Jun 2013 13:11:24 -0700 (PDT) [thread overview]
Message-ID: <51AF9B6C.1030006@oracle.com> (raw)
In-Reply-To: <cover.1370388945.git.joe@perches.com>
On 06/04/2013 06:39 PM, Joe Perches wrote:
> The second patch is speculative and maybe not necessary.
>
> Is a 3KB reduction in object size when embedded and !CONFIG_PRINTK worth it?
I'm pushing the first patch to linux-next. I haven't made up my mind
about the second. I don't really consider jfs to be the filesystem of
choice for a small embedded system. Maybe something like a dvr, but then
it wouldn't be a big factor.
Thanks
Shagggy
> Joe Perches (2):
> jfs: Update jfs_error
> jfs: Reduce object size when CONFIG_PRINTK=n
>
> fs/jfs/jfs_dmap.c | 70 +++++++++++++++++++------------------------------
> fs/jfs/jfs_dtree.c | 37 +++++++++++++-------------
> fs/jfs/jfs_extent.c | 2 +-
> fs/jfs/jfs_imap.c | 69 ++++++++++++++++++++----------------------------
> fs/jfs/jfs_metapage.c | 5 ++--
> fs/jfs/jfs_superblock.h | 17 +++++++++++-
> fs/jfs/jfs_txnmgr.c | 2 +-
> fs/jfs/jfs_xtree.c | 62 +++++++++++++++++++++----------------------
> fs/jfs/namei.c | 2 +-
> fs/jfs/resize.c | 2 +-
> fs/jfs/super.c | 24 ++++++++++-------
> fs/jfs/xattr.c | 4 +--
> 12 files changed, 142 insertions(+), 154 deletions(-)
>
prev parent reply other threads:[~2013-06-05 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 23:39 [PATCH 0/2] jfs: neatening Joe Perches
2013-06-04 23:39 ` [PATCH 1/2] jfs: Update jfs_error Joe Perches
2013-06-04 23:39 ` [PATCH 2/2] jfs: Reduce object size when CONFIG_PRINTK=n Joe Perches
2013-06-05 20:11 ` Dave Kleikamp [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=51AF9B6C.1030006@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox