All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Pavlos Parissis <pavlos.parissis@gmail.com>,
	Alexander Duyck <alexander.duyck@gmail.com>
Cc: "Anders K. Pedersen | Cohaesio" <akp@cohaesio.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"alexander.h.duyck@intel.com" <alexander.h.duyck@intel.com>
Subject: Re: Linux 4.12+ memory leak on router with i40e NICs
Date: Tue, 17 Oct 2017 01:34:29 +0200	[thread overview]
Message-ID: <39696136-2a4a-9c6c-3a63-4485ed2a1bf3@itcare.pl> (raw)
In-Reply-To: <3d783736-a474-d9e3-2de2-e35c765f8249@itcare.pl>



W dniu 2017-10-16 o 18:26, Paweł Staszewski pisze:
>
>
> W dniu 2017-10-16 o 13:20, Pavlos Parissis pisze:
>> On 15/10/2017 02:58 πμ, Alexander Duyck wrote:
>>> Hi Pawel,
>>>
>>> To clarify is that Dave Miller's tree or Linus's that you are talking
>>> about? If it is Dave's tree how long ago was it you pulled it since I
>>> think the fix was just pushed by Jeff Kirsher a few days ago.
>>>
>>> The issue should be fixed in the following commit:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/drivers/net/ethernet/intel/i40e/i40e_txrx.c?id=2b9478ffc550f17c6cd8c69057234e91150f5972 
>>>
>>>
>>
>> Do you know when it is going to be available on net-next and 
>> linux-stable repos?
>>
>> Cheers,
>> Pavlos
>>
>>
> I will make some tests today night with "net" git tree where this 
> patch is included.
> Starting from 0:00 CET
> :)
>
>
Upgraded and looks like problem is not solved with that patch
Currently running system with
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/
kernel

Still about 0.5GB of memory is leaking somewhere

Also can confirm that the latest kernel where memory is not leaking 
(with use i40e driver intel 710 cards) is 4.11.12
With kernel 4.11.12 - after hour no change in memory usage.

also checked that with ixgbe instead of i40e with same  net.git kernel 
there is no memleak - after hour same memory usage - so for 100% this is 
i40e driver problem.

WARNING: multiple messages have this Message-ID (diff)
From: =?unknown-8bit?q?Pawe=C5=82?= Staszewski <pstaszewski@itcare.pl>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Linux 4.12+ memory leak on router with i40e NICs
Date: Tue, 17 Oct 2017 01:34:29 +0200	[thread overview]
Message-ID: <39696136-2a4a-9c6c-3a63-4485ed2a1bf3@itcare.pl> (raw)
In-Reply-To: <3d783736-a474-d9e3-2de2-e35c765f8249@itcare.pl>



W dniu 2017-10-16 o?18:26, Pawe? Staszewski pisze:
>
>
> W dniu 2017-10-16 o?13:20, Pavlos Parissis pisze:
>> On 15/10/2017 02:58 ??, Alexander Duyck wrote:
>>> Hi Pawel,
>>>
>>> To clarify is that Dave Miller's tree or Linus's that you are talking
>>> about? If it is Dave's tree how long ago was it you pulled it since I
>>> think the fix was just pushed by Jeff Kirsher a few days ago.
>>>
>>> The issue should be fixed in the following commit:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/drivers/net/ethernet/intel/i40e/i40e_txrx.c?id=2b9478ffc550f17c6cd8c69057234e91150f5972 
>>>
>>>
>>
>> Do you know when it is going to be available on net-next and 
>> linux-stable repos?
>>
>> Cheers,
>> Pavlos
>>
>>
> I will make some tests today night with "net" git tree where this 
> patch is included.
> Starting from 0:00 CET
> :)
>
>
Upgraded and looks like problem is not solved with that patch
Currently running system with
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/
kernel

Still about 0.5GB of memory is leaking somewhere

Also can confirm that the latest kernel where memory is not leaking 
(with use i40e driver intel 710 cards) is 4.11.12
With kernel 4.11.12 - after hour no change in memory usage.

also checked that with ixgbe instead of i40e with same? net.git kernel 
there is no memleak - after hour same memory usage - so for 100% this is 
i40e driver problem.




  reply	other threads:[~2017-10-16 23:34 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 12:56 Linux 4.12+ memory leak on router with i40e NICs Anders K. Pedersen | Cohaesio
2017-10-04 12:56 ` [Intel-wired-lan] " Anders K. Pedersen | Cohaesio
2017-10-04 15:32 ` Alexander Duyck
2017-10-04 15:32   ` [Intel-wired-lan] " Alexander Duyck
2017-10-05  5:19   ` Anders K. Pedersen | Cohaesio
2017-10-05  5:19     ` [Intel-wired-lan] " Anders K. Pedersen | Cohaesio
2017-10-14 22:00     ` =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-14 22:03       ` =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-15  0:58         ` Alexander Duyck
2017-10-15  0:58           ` [Intel-wired-lan] " Alexander Duyck
2017-10-15 15:03           ` Paweł Staszewski
2017-10-15 15:03             ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-16 11:20           ` Pavlos Parissis
2017-10-16 11:20             ` [Intel-wired-lan] " Pavlos Parissis
2017-10-16 14:11             ` Alexander Duyck
2017-10-16 14:11               ` [Intel-wired-lan] " Alexander Duyck
2017-10-16 16:26             ` Paweł Staszewski
2017-10-16 16:26               ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-16 23:34               ` Paweł Staszewski [this message]
2017-10-16 23:34                 ` =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-16 23:56                 ` Alexander Duyck
2017-10-16 23:56                   ` [Intel-wired-lan] " Alexander Duyck
2017-10-17  0:44                   ` Paweł Staszewski
2017-10-17  0:44                     ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17  9:48                     ` Paweł Staszewski
2017-10-17  9:48                       ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 10:20                       ` Paweł Staszewski
2017-10-17 10:20                         ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 10:51                         ` Paweł Staszewski
2017-10-17 10:51                           ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 10:59                           ` Paweł Staszewski
2017-10-17 10:59                             ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 11:05                             ` Paweł Staszewski
2017-10-17 11:05                               ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 11:52                               ` Paweł Staszewski
2017-10-17 11:52                                 ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-17 14:08                                 ` Paweł Staszewski
2017-10-17 14:08                                   ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 15:44                                   ` Paweł Staszewski
2017-10-18 15:44                                     ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 22:20                                     ` Paweł Staszewski
2017-10-18 22:20                                       ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 22:50                                       ` Paweł Staszewski
2017-10-18 22:50                                         ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 22:58                                         ` Paweł Staszewski
2017-10-18 22:58                                           ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 23:22                                           ` Paweł Staszewski
2017-10-18 23:22                                             ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 23:37                                             ` Alexander Duyck
2017-10-18 23:37                                               ` [Intel-wired-lan] " Alexander Duyck
2017-10-18 23:51                                               ` Paweł Staszewski
2017-10-18 23:51                                                 ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 23:56                                                 ` Paweł Staszewski
2017-10-18 23:56                                                   ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-18 23:59                                                   ` Paweł Staszewski
2017-10-18 23:59                                                     ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-19 17:10                                                 ` Alexander Duyck
2017-10-19 17:10                                                   ` [Intel-wired-lan] " Alexander Duyck
2017-10-19 12:19                                               ` Anders K. Pedersen | Cohaesio
2017-10-19 12:19                                                 ` [Intel-wired-lan] " Anders K. Pedersen | Cohaesio
2017-10-19 15:40                                                 ` Alexander Duyck
2017-10-19 15:40                                                   ` [Intel-wired-lan] " Alexander Duyck
2017-10-22 13:56                                                   ` Anders K. Pedersen | Cohaesio
2017-10-22 13:56                                                     ` [Intel-wired-lan] " Anders K. Pedersen | Cohaesio
2017-10-17  5:51                 ` Vitezslav Samel
2017-10-17  5:51                   ` [Intel-wired-lan] " Vitezslav Samel
2017-10-18 23:29                   ` Alexander Duyck
2017-10-18 23:29                     ` [Intel-wired-lan] " Alexander Duyck
2017-10-18 23:40                     ` Paweł Staszewski
2017-10-18 23:40                       ` [Intel-wired-lan] " =?unknown-8bit?q?Pawe=C5=82?= Staszewski
2017-10-19 11:41                       ` Pavlos Parissis
2017-10-19 11:41                         ` [Intel-wired-lan] " Pavlos Parissis
2017-10-19 15:53                         ` Alexander Duyck
2017-10-19 15:53                           ` [Intel-wired-lan] " Alexander Duyck

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=39696136-2a4a-9c6c-3a63-4485ed2a1bf3@itcare.pl \
    --to=pstaszewski@itcare.pl \
    --cc=akp@cohaesio.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavlos.parissis@gmail.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 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.