From: David Miller <davem@davemloft.net>
To: oneukum@suse.com
Cc: jim_baxter@mentor.com, bjorn@mork.no, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC V1 1/1] net: cdc_ncm: Reduce memory use when kernel memory low
Date: Tue, 23 May 2017 11:26:25 -0400 (EDT) [thread overview]
Message-ID: <20170523.112625.33559883707681029.davem@davemloft.net> (raw)
In-Reply-To: <1495528968.2174.2.camel@suse.com>
From: Oliver Neukum <oneukum@suse.com>
Date: Tue, 23 May 2017 10:42:48 +0200
> Am Montag, den 22.05.2017, 11:54 -0400 schrieb David Miller:
>>
>> Unfortunately without a real notifier of some sort (there isn't one, and
>> it isn't actually easy to come up with a clean way to do this which is
>> probably why it doesn't exist yet in the first place) I really cannot
>> recommend anything better.
>>
>> That being said, probably for the time being we should just backoff each
>> and every request, always trying initially to do the higher order thing.
>
> We could use a counter. After the first failure, do it once, after the
> second twice and so on. And reset the counter as a higher order
> allocation works. (just bound it somewhere)
So an exponential backoff, that might work.
next prev parent reply other threads:[~2017-05-23 15:26 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
[not found] ` <1494956480-6127-1-git-send-email-jim_baxter-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-05-16 17:41 ` [RFC V1 1/1] net: cdc_ncm: Reduce " Jim Baxter
2017-05-16 18:24 ` Bjørn Mork
[not found] ` <87shk4fynp.fsf-3F4PFWf5pNjpjLOzFPqGjWGXanvQGlWp@public.gmane.org>
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
2017-05-22 15:54 ` David Miller
2017-05-23 8:42 ` Oliver Neukum
2017-05-23 15:26 ` David Miller [this message]
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
[not found] ` <063D6719AE5E284EB5DD2968C1650D6DCFFFAC2B-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
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=20170523.112625.33559883707681029.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjorn@mork.no \
--cc=jim_baxter@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
/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).