From: Marek Szyprowski <m.szyprowski@samsung.com>
To: 'Haojian Zhuang' <haojian.zhuang@gmail.com>,
'Christoph Lameter' <cl@linux.com>
Cc: linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org
Subject: RE: how to avoid allocating or freeze MOVABLE memory in userspace
Date: Fri, 11 May 2012 15:27:49 +0200 [thread overview]
Message-ID: <035501cd2f79$dbfde410$93f9ac30$%szyprowski@samsung.com> (raw)
In-Reply-To: <CAN1soZyJ_zURkhV3aav5oQ6gU1CcQLsUsQKDe38gdOhapkc8jw@mail.gmail.com>
Hello,
On Wednesday, April 18, 2012 9:37 AM Haojian Zhuang wrote:
> On Mon, Apr 16, 2012 at 9:55 PM, Christoph Lameter <cl@linux.com> wrote:
> > On Sat, 14 Apr 2012, Haojian Zhuang wrote:
> >
> >> On Sat, Apr 14, 2012 at 2:27 AM, Christoph Lameter <cl@linux.com> wrote:
> >> > On Fri, 13 Apr 2012, Haojian Zhuang wrote:
> >> >
> >> >> I have one question on memory migration. As we know, malloc() from
> >> >> user app will allocate MIGRATE_MOVABLE pages. But if we want to use
> >> >> this memory as DMA usage, we can't accept MIGRATE_MOVABLE type. Could
> >> >> we change its behavior before DMA working?
> >> >
> >> > MIGRATE_MOVABLE works fine for DMA. If you keep a reference from a device
> >> > driver to user pages then you will have to increase the page refcount
> >> > which will in turn pin the page and make it non movable for as long as you
> >> > keep the refcount.
> >>
> >> Hi Christoph,
> >>
> >> Thanks for your illustration. But it's a little abstract. Could you
> >> give me a simple example
> >> or show me the code?
> >
> > Run get_user_pages() on the memory you are interest in pinning. See how
> > other drivers do that by looking up other use cases. F.e. ib_umem_get()
> > does a similar thing.
> >
> >
> Got it. And I think there's conflict in CMA.
>
> For example, user process A malloc() memory, page->_count is 1. After
> using get_user_pages()
> in device driver for DMA usage, page->_count becomes 2.
>
> If the page is in CMA region, it results migrate_pages() returns
> -EAGAIN. But error handling in CMA is in below.
>
> ret = alloc_contig_range(pfn, pfn + count, MIGRATE_CMA);
> if (ret == 0) {
> bitmap_set(cma->bitmap, pageno, count);
> break;
> } else if (ret != -EBUSY) {
> goto error;
> }
>
> Since EAGAIN doesn't equal to EBUSY, dma_alloc_from_contiguous()
> aborts. Should dma_alloc_from_contiguous() handle EAGAIN?
>
I've checked again and it is really not possible for migrate_pages() to return -EAGAIN,
so the CMA code is correct. The only special case which needs retry is -EBUSY.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-05-11 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:35 Haojian Zhuang
2012-04-13 18:27 ` Christoph Lameter
2012-04-14 2:51 ` Haojian Zhuang
2012-04-16 13:55 ` Christoph Lameter
2012-04-18 7:36 ` Haojian Zhuang
2012-04-18 13:49 ` Christoph Lameter
2012-04-18 15:10 ` Marek Szyprowski
2012-05-11 13:27 ` Marek Szyprowski [this message]
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='035501cd2f79$dbfde410$93f9ac30$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=cl@linux.com \
--cc=haojian.zhuang@gmail.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox