From: John Weber <rjohnweber@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Right lib-imx/firmware-imx ... versions
Date: Mon, 04 Aug 2014 10:41:21 -0500 [thread overview]
Message-ID: <53DFA9A1.8060007@gmail.com> (raw)
In-Reply-To: <04142B7D-669C-4114-A990-CEC915F8ECF2@gmail.com>
Hi Jens-
On 8/2/14, 9:59 AM, Jens Rehsack wrote:
> Daiane, because you also was involved into https://community.freescale.com/thread/304414:
>
> I digged a lot deeper, tried https://github.com/wandboard-org/linux/commit/7cbd06b2904c1855109084ca6b0c84990bc69233
> and debugged and proved more there ...
Have you forward-ported this to 3.10.17? If so, it seems that the only downside
for this is that it preallocates a lot of memory for the VPU. It really
shouldn't be necessary as long as page caching works properly, as I understand it.
> I also tried to get a picture of vmm by browsing "Understanding The Linux Virtual Memory Manager" by Mel Gorman.
>
> My result: When no swap is configured (and the box has none - because of 1GB RAM and 4GB Flash there is not really space for swap), the memory runs full by page-caching disk files.
Are you seeing some error messages here that you can post?
>
> There could be several ways out to ensure system is not crashing when pages for DMA are allocated by eg. XBMC, gplay or whatever wants to use the VPU.
>
> 1) continuously drop page cache (our measurement tells in our configuration every 15sec is fine even for 4K movies)
> 2) implement better dma page cache as v4l2 patch demonstrates (pre-alloc 256M and serve dma pages from there, use smart allocation as SmartHeap does and https://github.com/wandboard-org/linux/commit/7cbd06b2904c1855109084ca6b0c84990bc69233 drafts ...)
> 3) modify vpu dma allocator to interfere with page cache and drop oldest cache entries
> 4) find a way to simulate swap-conditions without really paging out
This (4) seems like a hack. We need to be able to turn off swap without having
to simulate it.
>
> Any hints choosing the optimal decision will be appreciated :)
>
> Best regards
next prev parent reply other threads:[~2014-08-04 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 5:24 Right lib-imx/firmware-imx ... versions Jens Rehsack
2014-07-23 3:57 ` Jens Rehsack
2014-07-23 14:19 ` Daiane Angolini
2014-07-23 14:51 ` Jens Rehsack
2014-07-23 15:14 ` xxiao8
2014-07-23 15:46 ` Daiane Angolini
2014-07-23 15:45 ` Daiane Angolini
2014-07-23 17:31 ` Jens Rehsack
2014-08-02 14:59 ` Jens Rehsack
2014-08-04 15:41 ` John Weber [this message]
2014-08-04 19:04 ` Jens Rehsack
2014-08-04 19:48 ` John Weber
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=53DFA9A1.8060007@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.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.