From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Kernelnewbies@kernelnewbies.org
Subject: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
Date: Fri, 26 Jun 2020 16:30:48 +0800 [thread overview]
Message-ID: <CAAvDm6bf=c0gC6U92L1VJc_vQpvks-2H=F8rrdwKxGaBLH8Arw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 402 bytes --]
Hi, list
Besides kmalloc() is more efficient, are there some potential problems that
I should be aware of if I allocate the memory which doesn't have any
relation to peripheral hardwares(i.e. DMA,PCI,serial port and etc) by
vmalloc() instead of kmalloc() to avoid the page allocation failure(caused
by kmalloc() while there are too much memory fragment)?
Thank you for your attention to this matter.
[-- Attachment #1.2: Type: text/html, Size: 481 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-06-26 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 8:30 孙世龙 sunshilong [this message]
2020-06-26 14:13 ` Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()? Greg KH
2020-06-26 15:36 ` 孙世龙 sunshilong
2020-06-26 17:22 ` Valdis Klētnieks
2020-06-27 5:16 ` 孙世龙 sunshilong
2020-06-27 5:23 ` Greg KH
2020-06-27 6:00 ` 孙世龙 sunshilong
2020-06-27 7:05 ` Greg KH
2020-06-27 5:05 ` Greg KH
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='CAAvDm6bf=c0gC6U92L1VJc_vQpvks-2H=F8rrdwKxGaBLH8Arw@mail.gmail.com' \
--to=sunshilong369@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).