From: "Richard Röjfors" <richard.rojfors@pelagicore.com>
To: Pawel Osciak <p.osciak@samsung.com>
Cc: 'Linux Media Mailing List' <linux-media@vger.kernel.org>,
'Mauro Carvalho Chehab' <mchehab@redhat.com>,
'Douglas Schilling Landgraf' <dougsland@gmail.com>,
'Samuel Ortiz' <sameo@linux.intel.com>
Subject: Re: [PATCH 1/3 v2] media: Add a cached version of the contiguous video buffers
Date: Wed, 04 Aug 2010 13:37:35 +0200 [thread overview]
Message-ID: <4C5950FF.4010705@pelagicore.com> (raw)
In-Reply-To: <001201cb33c0$af683290$0e3897b0$%osciak@samsung.com>
On 08/04/2010 12:34 PM, Pawel Osciak wrote:
>> Richard Röjfors<richard.rojfors@pelagicore.com> wrote:
>> On 08/04/2010 11:50 AM, Pawel Osciak wrote:
>>>>
>>>> How do you propose to allocate the buffers? They need to be contiguous
>>>> and using uncached memory gave really bad performance.
>>>
>>> 829440 bytes is a quite a lot and one can't reliably depend on kmalloc
>>> to be able to allocate such big chunks of contiguous memory. Were you
>>> testing this on a freshly rebooted system?
>>
>> The systems have been running for a while, but not days.
>> I don't see why would dma_alloc_coherent work better than kmalloc?
>>
>
> In principle it wouldn't. It's just it's much less intensively used and
> allocates from a special area. Not really a bullet-proof solution either
> though, I agree.
So what is your proposal given the current situation?
Using dma_alloc_noncoherent instead of kmalloc and use dma_cache_sync
instead of dma_sync_single_for_cpu?
--Richard
next prev parent reply other threads:[~2010-08-04 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:18 [PATCH 1/3 v2] media: Add a cached version of the contiguous video buffers Richard Röjfors
2010-08-04 7:55 ` Pawel Osciak
2010-08-04 9:40 ` Richard Röjfors
2010-08-04 9:50 ` Pawel Osciak
2010-08-04 10:03 ` Richard Röjfors
2010-08-04 10:34 ` Pawel Osciak
2010-08-04 11:37 ` Richard Röjfors [this message]
2010-08-05 20:25 ` Richard Röjfors
2010-08-09 8:50 ` Pawel Osciak
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=4C5950FF.4010705@pelagicore.com \
--to=richard.rojfors@pelagicore.com \
--cc=dougsland@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=p.osciak@samsung.com \
--cc=sameo@linux.intel.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