From: "Michal Nazarewicz" <mina86@mina86.com>
To: "Barry Song" <Barry.Song@csr.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>
Cc: m.szyprowski@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, workgroup.linux@csr.com,
"Barry Song" <Baohua.Song@csr.com>
Subject: Re: [PATCH v3] MM: CMA: add a simple kernel module as the helper to test CMA
Date: Wed, 07 Mar 2012 11:48:24 +0100 [thread overview]
Message-ID: <op.wasqyyok3l0zgt@mpn-glaptop> (raw)
In-Reply-To: <4F56E0AC.8070501@gmail.com>
> On 03/07/2012 11:14 AM, Barry Song wrote:
>> Any write request to /dev/cma_test will let the module to allocate memory from
>> CMA, for example:
>>
>> 1st time
>> $ echo 1024> /dev/cma_test
>> will require cma_test to request 1MB(1024KB)
>> 2nd time
>> $ echo 2048> /dev/cma_test
>> will require cma_test to request 2MB(2048KB)
>>
>> Any read request to /dev/cma_test will let the module to free the 1st valid
>> memory from CMA, for example:
>>
>> 1st time
>> $ cat /dev/cma_test
>> will require cma_test to free the 1MB allocated in the first write request
>> 2nd time
>> $ cat /dev/cma_test
>> will require cma_test to free the 2MB allocated in the second write request
On Wed, 07 Mar 2012 05:14:36 +0100, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> Any reason why using /dev not /proc or /sys?
Because /proc is for processes and /sys is for stable, documented APIs.
If anything, debugfs might make some sense, but since the module needs struct
device anyway, it can just register a misc device, which is simpler and does
not require debugfs to be compiled.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
next prev parent reply other threads:[~2012-03-07 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 3:14 Barry Song
2012-03-07 4:14 ` Cong Wang
2012-03-07 4:49 ` Barry Song
2012-03-07 4:55 ` Cong Wang
2012-03-07 4:57 ` Barry Song
2012-03-07 5:01 ` Cong Wang
2012-03-07 5:05 ` Barry Song
2012-03-07 5:09 ` Cong Wang
2012-03-07 5:17 ` Barry Song
2012-03-07 5:22 ` Cong Wang
2012-03-07 5:40 ` Barry Song
2012-03-07 10:38 ` Barry Song
2012-03-07 10:48 ` Michal Nazarewicz [this message]
2012-03-07 10:55 ` Barry Song
2012-03-07 10:59 ` Michal Nazarewicz
2012-03-07 11:12 ` Barry Song
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=op.wasqyyok3l0zgt@mpn-glaptop \
--to=mina86@mina86.com \
--cc=Baohua.Song@csr.com \
--cc=Barry.Song@csr.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=workgroup.linux@csr.com \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®