From: "Baxter, Jim" <jim_baxter@mentor.com>
To: David Miller <davem@davemloft.net>, <bjorn@mork.no>
Cc: <linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <oliver@neukum.org>
Subject: Re: [RFC V1 1/1] net: cdc_ncm: Reduce memory use when kernel memory low
Date: Mon, 22 May 2017 16:45:42 +0100 [thread overview]
Message-ID: <04bc5b49-9282-a6ca-2b95-fb8fc9750555@mentor.com> (raw)
In-Reply-To: <20170517.141819.1307166900606639947.davem@davemloft.net>
From: David S. Miller (davem@davemloft.net)
Sent: Wed, 17 May 2017 14:18:19 -0400
>
> When there isn't memory pressure this will hurt performance of
> course.
>
> It is a quite common paradigm to back down to 0 order memory requests
> when higher order ones fail, so this isn't such a bad change from the
> perspective.
>
> However, one negative about it is that when the system is under memory
> stress it doesn't help at all to keep attemping high order allocations
> when the system hasn't recovered yet. In fact, this can make it
> worse.
>
Hello David,
Do you think the patch should be modified to extend the length of time
the 0 order memory requests with a time period of 1 minute for example?
Or do you feel the patch is not the correct way this should be performed?
Best regards,
Jim
next prev parent reply other threads:[~2017-05-22 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:41 [RFC V1 0/1] Reduce cdc_ncm memory use when kernel memory low Jim Baxter
2017-05-16 17:41 ` [RFC V1 1/1] net: cdc_ncm: Reduce " Jim Baxter
2017-05-16 18:24 ` Bjørn Mork
2017-05-17 7:44 ` Oliver Neukum
2017-05-17 10:56 ` Baxter, Jim
2017-05-17 18:18 ` David Miller
2017-05-18 10:01 ` Oliver Neukum
2017-05-22 15:45 ` Baxter, Jim [this message]
2017-05-22 15:54 ` David Miller
2017-05-23 8:42 ` Oliver Neukum
2017-05-23 15:26 ` David Miller
2017-05-23 19:06 ` Baxter, Jim
[not found] ` <1497263047.15677.13.camel@suse.com>
2017-06-12 12:32 ` Baxter, Jim
2017-05-19 11:10 ` David Laight
2017-05-19 13:55 ` Bjørn Mork
2017-05-19 14:46 ` David Laight
2017-05-22 13:27 ` Oliver Neukum
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=04bc5b49-9282-a6ca-2b95-fb8fc9750555@mentor.com \
--to=jim_baxter@mentor.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.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).