From: "Bjørn Mork" <bjorn@mork.no>
To: "Baxter\, Jim" <jim_baxter@mentor.com>
Cc: <linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Oliver Neukum <oliver@neukum.org>,
David Laight <David.Laight@ACULAB.COM>
Subject: Re: [PATCH V2 1/1] net: cdc_ncm: Reduce memory use when kernel memory low
Date: Fri, 30 Jun 2017 20:03:40 +0200 [thread overview]
Message-ID: <8760fds683.fsf@miraculix.mork.no> (raw)
In-Reply-To: <356bdf94-813d-94ef-4dc3-a582fe5b3343@mentor.com> (Jim Baxter's message of "Fri, 30 Jun 2017 18:53:56 +0100")
"Baxter, Jim" <jim_baxter@mentor.com> writes:
> I tested this with printk's to show when the low memory code was triggered
> and the value of ctx->tx_low_mem_val and ctx->tx_low_mem_max_cnt.
> I created a workqueue that slowly used up the atomic memory until the
> code is triggered.
>
> I could add debug prints, though I have noticed that cdc_ncm_fill_tx_frame()
> does not currently have any debug prints do you think this is because it can be
> called in an atomic context and I think debug messages if enabled could cause
> too great a delay?
Yes, I guess you're right. Maybe count the number of failed allocations
and export it along with the other driver private counters? Or export
the tx_curr_size as a sysfs attribute? Or both?
Just an idea... I don't expect to see this code ever being hit on my
systems :-)
Bjørn
next prev parent reply other threads:[~2017-06-30 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 20:35 [PATCH V2 0/1] Reduce cdc_ncm " Jim Baxter
2017-06-28 20:35 ` [PATCH V2 1/1] net: cdc_ncm: Reduce " Jim Baxter
2017-06-30 16:59 ` David Miller
2017-06-30 17:03 ` Baxter, Jim
2017-06-30 17:38 ` Bjørn Mork
2017-06-30 17:53 ` Baxter, Jim
2017-06-30 18:03 ` Bjørn Mork [this message]
2017-07-03 8:51 ` David Miller
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=8760fds683.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=David.Laight@ACULAB.COM \
--cc=jim_baxter@mentor.com \
--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
Powered by JetHome