From: Ranran <ranshalit@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: vmalloc_to_page is contiguous ?
Date: Mon, 18 Mar 2019 12:55:17 +0200 [thread overview]
Message-ID: <CAJ2oMhLSDndr2LgFkin-r-eh8UfXf0MfGCAPp8kDGLqZQjdaPw@mail.gmail.com> (raw)
Hello,
Does vmalloc_to_page() returns contiguous physical memory ?
I ask becuase I see that its return value is used for DMA and DMA uses
contiguous memory.
see here:
https://elixir.bootlin.com/linux/latest/source/drivers/mtd/nand/onenand/samsung.c#L657
Yet, in vmalloc_to_page implementation:
https://elixir.bootlin.com/linux/v4.5/source/mm/vmalloc.c#L234
it does not seem that it creates a contiguous allocation.
Thank you,
ranran
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-03-18 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:55 Ranran [this message]
2019-03-18 18:00 ` vmalloc_to_page is contiguous ? Rik van Riel
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=CAJ2oMhLSDndr2LgFkin-r-eh8UfXf0MfGCAPp8kDGLqZQjdaPw@mail.gmail.com \
--to=ranshalit@gmail.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).