public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: "Paweł Staszewski" <pstaszewski@itcare.pl>,
	"Linux Kernel Network Developers" <netdev@vger.kernel.org>
Subject: Re: Huge memory leak with 4.15.0-rc2+
Date: Mon, 11 Dec 2017 14:15:45 -0800	[thread overview]
Message-ID: <65a3563d-396e-e4fb-7dad-937ce999868e@gmail.com> (raw)
In-Reply-To: <2353c149-cae1-f986-63d0-3568534a1e8c@itcare.pl>

On 12/11/2017 01:48 PM, Paweł Staszewski wrote:
> 
> 
> W dniu 2017-12-11 o 22:23, Paweł Staszewski pisze:
>> Hi
>>
>>
>> I just upgraded some testing host to 4.15.0-rc2+ kernel
>>
>> And after some time of traffic processing - when traffic on all ports
>> reach about 3Mpps - memleak started.
>>


[...]

>> Some observations - when i disable tso on all cards there is more
>> memleak.
>>
>>
>>
>>
>>
> When traffic starts to drop - there is less and less memleak
> below link to memory usage graph:
> https://ibb.co/hU97kG
> 
> And there is rising slab_unrecl - Amount of unreclaimable memory used
> for slab kernel allocations
> 
> 
> Forgot to add that im using hfsc and qdiscs like pfifo on classes.
> 
> 

Maybe some error case I missed in the qdisc patches I'm looking into
it.

Thanks,
John

  reply	other threads:[~2017-12-11 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 21:23 Huge memory leak with 4.15.0-rc2+ Paweł Staszewski
2017-12-11 21:48 ` Paweł Staszewski
2017-12-11 22:15   ` John Fastabend [this message]
2017-12-11 22:27     ` Paweł Staszewski
2017-12-12 17:57       ` Paweł Staszewski
2017-12-13 21:05         ` John Fastabend

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=65a3563d-396e-e4fb-7dad-937ce999868e@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pstaszewski@itcare.pl \
    /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