[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGsJ_4x4CwD+WAE9d+Xob_tfwqmE6SdBdBd5EbC64XBi4Uzvgg@mail.gmail.com>
Date: Wed, 7 Mar 2012 12:49:21 +0800
From: Barry Song <21cnbao@...il.com>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: Barry Song <Barry.Song@....com>, linux-kernel@...r.kernel.org,
workgroup.linux@....com, mina86@...a86.com,
Barry Song <Baohua.Song@....com>,
linux-arm-kernel@...ts.infradead.org, m.szyprowski@...sung.com
Subject: Re: [PATCH v3] MM: CMA: add a simple kernel module as the helper to
test CMA
2012/3/7 Cong Wang <xiyou.wangcong@...il.com>:
> On 03/07/2012 11:14 AM, Barry Song wrote:
>>
>> From: Barry Song<Baohua.Song@....com>
>>
>> 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
>
>
> Any reason why using /dev not /proc or /sys?
pls note it is just a test module to verify CMA at runtime. it is not
important either it is /dev, it is /proc or it is /sys.
any way to make things easier, we take that way.
-barry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists