From: Luigi Semenzato <semenzato@google.com>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-mm@kvack.org, Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>
Subject: Re: zram on ARM
Date: Fri, 2 Nov 2012 16:27:47 -0700 [thread overview]
Message-ID: <CAA25o9SXNHFgQmVMNmGNwPDCRpRTsRDW8oRvnLyofGrVo6bnNQ@mail.gmail.com> (raw)
In-Reply-To: <20121102225341.GC2070@barrios>
On Fri, Nov 2, 2012 at 3:53 PM, Minchan Kim <minchan@kernel.org> wrote:
> Hi Luigi,
>
> I am embarrassed because recently I have tried to promote zram
> from staging tree.
>
> I thought it's very stable because our production team already have
> used recent zram on ARM and they don't report any problem to me until now.
> But I'm not sure how they use it stressfully so I will check it.
> And other many project of android have used it but I doubt it's recent zram
> so it would be a problem of recent patch.
>
> Anyway I will look at it but unfortunately, as I said earlier, I should go
> to training course during 2 weeks. So reply will be late.
> I hope other people involve in during that.
>
> Thanks for the reporting.
No, it is I who should be embarrassed because my results were
premature and I jumped the gun. The backport of ToT to 3.4 didn't
work correctly, even if it compiled. I was getting OOPSes in zram
data transfers on x86---never mind ARM.
I am now trying a safer approach, by just applying the patch that
removes the x86 dependency. I have tested that change on x86 and it
works fine (perhaps a bit more sluggish? Could be subjective). I am
still working on getting the ARM side properly tested.
Thank you and I hope your training goes well.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-02 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 19:59 Luigi Semenzato
2012-11-02 20:52 ` Luigi Semenzato
2012-11-02 22:53 ` Minchan Kim
2012-11-02 23:27 ` Luigi Semenzato [this message]
2012-11-03 0:04 ` Luigi Semenzato
2012-11-03 0:09 ` Luigi Semenzato
2012-11-05 21:12 ` Luigi Semenzato
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=CAA25o9SXNHFgQmVMNmGNwPDCRpRTsRDW8oRvnLyofGrVo6bnNQ@mail.gmail.com \
--to=semenzato@google.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.com \
/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