From: greg kh <greg@kroah.com>
To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Re: How to avoid or reduce GFP_ATOMIC allocation failed
Date: Fri, 8 Mar 2019 08:40:36 +0100 [thread overview]
Message-ID: <20190308074035.GA16279@kroah.com> (raw)
In-Reply-To: <c8a7ec0.a501.1695c396413.Coremail.wuzhouhui14@mails.ucas.ac.cn>
On Fri, Mar 08, 2019 at 03:34:18PM +0800, wuzhouhui wrote:
> > -----Original Messages-----
> > From: "Greg KH" <greg@kroah.com>
> > Sent Time: 2019-03-08 15:21:52 (Friday)
> > To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
> > Cc: kernelnewbies@kernelnewbies.org
> > Subject: Re: How to avoid or reduce GFP_ATOMIC allocation failed
> >
> > On Fri, Mar 08, 2019 at 01:37:26PM +0800, wuzhouhui wrote:
> > > Hi,
> > >
> > > I check kernel code and found that GFP_ATOMIC allocation will
> > > use emergency pool and maybe failed if emergency pool is not
> > > enough. And GFP_ATOMIC doesn't trigger reclaim (because of
> > > ATOMIC) even if there are a lot of page caches. So my question
> > > is how to avoid or reduce GFP_ATOMIC allocation failed if there
> > > are enough reclaimable memory? Is there some kernel parameters
> > > can be configured?
> >
> > Have you seen the ATOMIC pools be used up and not able to be reclaimed
> > in real-world usages? If so, I'm sure the mm developers would love to
>
> No, I haven't seen this scenario. But I encountered the similar issue
> with [1] (order is 5 in my scenario), and this issue is not resolved for
> now.
Please work with the company that created your out-of-tree kernel
networking code as it sounds like they do not know how to properly
handle this type of problem :)
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-03-08 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 5:37 How to avoid or reduce GFP_ATOMIC allocation failed wuzhouhui
2019-03-08 7:21 ` Greg KH
2019-03-08 7:34 ` wuzhouhui
2019-03-08 7:40 ` greg kh [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=20190308074035.GA16279@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.