From: Rob Herring <robherring2@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 1/2] ext4fs ls load support
Date: Tue, 27 Mar 2012 08:46:36 -0500 [thread overview]
Message-ID: <4F71C4BC.1080204@gmail.com> (raw)
In-Reply-To: <3011BF76E09343829CA4A8B33E64E2FF@sisodomain.com>
On 03/27/2012 08:13 AM, manjunatha wrote:
> Dear Rob Herring/ Wolfgang,
>
> As discussed in earlier mail chain, our current ext4 implementation is
> capable enough to list(ls) and read(load) ext2 partitons as well.
>
> Also the current ext4 implementation is optimized to 7-8 times greater
> read throughput than ext2load.
Cool. IIRC, there was just recently some discussion on the list about
ext2 performance problems.
> I propose that we can remove the existing ext2 code and let it be
> replaced with ext4.
That's exactly what I proposed. Although, I think your patch should be
done as modifications to cmd_ext2.c rather than deleting it and adding a
new cmd_ext4.c.
> All users using ext2ls and ext2load command can replace them with ext4ls
> and ext4load respectively.
I think you need to keep the command names to not break existing users'
scripts. So either we just stick with ext2ls/ext2load or define
additional ext4* commands which call the same functions as the ext2
version. I don't really care, but would lean toward the former.
Rob
>
>
>
> The ext4 code is based on ext2 implementation and we have added the
> names of respective owners(ext2 code authors) in the file headers.
>
> Please suggest what could be the best approach.
>
>
>
> Thanks & Regards,
>
> Manjunatha C achar
>
>
>
> --------------------------------------------------
> From: "Rob Herring" <robherring2@gmail.com>
> Sent: Monday, March 26, 2012 6:40 PM
> To: <uma.shankar@samsung.com>
> Cc: <u-boot@lists.denx.de>; "MANJUNATHAC ACHAR"
> <a.manjunatha@samsung.com>; <kim.phillips@freescale.com>; "IQBAL
> SHAREEF" <iqbal.ams@samsung.com>; "HAKGOO LEE"
> <goodguy.lee@samsung.com>; <wd@denx.de>
> Subject: Re: [U-Boot] [PATCH V4 1/2] ext4fs ls load support
>
>> On 03/26/2012 02:24 AM, UMA SHANKAR wrote:
>>> Dear Rob Herring, Thanks for evaluating and testing our code.
>>> Currently, Our ext4 implementation is capable of listing and reading
>>> (ls and load) ext2 partitions as well. But, we wanted the ext4 code
>>> to be separate from ext2 implementation.
>>
>> Why?
>>
>>> Your comment: --- Using ext2 commands on an ext4 partition will hang
>>> now.
>>>
>>> ext2load command will only read ext2 partitions, and will definitely
>>> not work on ext4 (even without our implementation).
>>
>> I'm not saying it should work, but it shouldn't hang. IIRC without your
>> patch, it would return with an error. So you have changed something in
>> the core ext2 code that makes it hang. But it's not something I think
>> you need to worry about as the ext4 version of code should just replace
>> the ext2 version and the issue will go away.
>>
>> Rob
>>
>>> ? So, I propose, we can let both these implementations be there in
>>> uboot under different CONFIG Options (as is the case currently). ?
>>> Thanks & Regards, Uma Shankar
>
>
next prev parent reply other threads:[~2012-03-27 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27542660.71361332746650945.JavaMail.weblogic@epml04>
2012-03-26 9:16 ` [U-Boot] [PATCH V4 1/2] ext4fs ls load support Wolfgang Denk
2012-03-26 13:10 ` Rob Herring
2012-03-27 13:13 ` manjunatha
2012-03-27 13:46 ` Rob Herring [this message]
2012-03-27 22:21 ` Graeme Russ
2011-12-28 2:22 [U-Boot] [PATCH V3 " uma.shankar at samsung.com
2012-01-09 17:54 ` [U-Boot] [PATCH V4 " uma.shankar at samsung.com
2012-03-22 15:49 ` Rob Herring
2012-03-27 15:10 ` Rob Herring
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=4F71C4BC.1080204@gmail.com \
--to=robherring2@gmail.com \
--cc=u-boot@lists.denx.de \
/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