All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] genext2fs: support large files and filesystems without using large amounts of memor
Date: Fri, 30 Mar 2012 22:49:46 +0100	[thread overview]
Message-ID: <1333144186.18082.134.camel@ted> (raw)
In-Reply-To: <3ABC0140-1A7C-45A2-A601-3D8BDCB839D6@dominion.thruhere.net>

On Fri, 2012-03-30 at 13:43 -0700, Koen Kooi wrote:
> Op 29 mrt. 2012, om 15:07 heeft Richard Purdie het volgende geschreven:
> 
> > On Thu, 2012-03-29 at 00:51 +0800, Dexuan Cui wrote:
> >> Hi RP, Saul, Paul, Darren, Mark, Josh and joaohf and all, please comment.
> >> 
> >> Let's figure out if this big patch is accepatable or not...
> >> 
> >> With this patch, I can successfully create a 8.5GB .ext3 file with genext2fs.
> >> The speed is slow -- I spent about 1.5 hours.
> > 
> > If these patches solved all the problems and made things work
> > wonderfully I'd probably say we'd take them. Unfortunately I don't
> > consider taking 1.5 hours to build am 8GB filesystem "wonderful", its
> > rather worrying and I don't think its performing any where need fast
> > enough for our needs :(.
> > 
> > Patching genext2fs at this point in the cycle is a rather risky
> > undertaking too and I'm getting very concerned about this. 
> 
> The biggest issue I have with genext2fs is that it currently allocates
> RAM for the complete image, which in my case will cause it to swap and
> for other users cause it to crash, since image > (ram + swap). Fixing
> the memory issue before the release would be greatly appreciated.
> 
> What about putting it on the shortlist for backports after the
> release? That should give us all more time to test it and eventually
> get into the hands of stable branch users. Of course I'd still prefer
> it to go in before the release and backport fixes :)

I should point out one of the patches in this mega patch set is one for
the memory issue.

I'd appreciate some others giving this patch set a go, see if they can
find any regressions for their usual use cases.

Based on the feedback I've had so far I'm leaning towards merging it but
I'm not making a final decision yet, I'd like some test reports...

Cheers,

Richard




  reply	other threads:[~2012-03-30 21:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 16:51 [PATCH 0/1] genext2fs: support large files and filesystems without using large amounts of memor Dexuan Cui
2012-03-28 16:51 ` [PATCH 1/1] genext2fs: support large files and filesystems without using large amounts of memory Dexuan Cui
2012-03-29  8:57 ` [PATCH 0/1] genext2fs: support large files and filesystems without using large amounts of memor Cui, Dexuan
2012-03-29 22:07 ` Richard Purdie
2012-03-29 22:27   ` McClintock Matthew-B29882
2012-03-29 22:31     ` Paul Eggleton
2012-03-29 22:55   ` Darren Hart
2012-03-30 15:48     ` Cui, Dexuan
2012-03-30 20:43   ` Koen Kooi
2012-03-30 21:49     ` Richard Purdie [this message]
2012-03-30 21:50       ` Koen Kooi

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=1333144186.18082.134.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.