All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Qing Huang <qing.huang@oracle.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	John Sperbeck <jsperbeck@google.com>,
	Tarick Bedeir <tarick@google.com>,
	Daniel Jurgens <danielj@mellanox.com>,
	Zhu Yanjun <yanjun.zhu@oracle.com>
Subject: Re: [PATCH v2 net] mlx4_core: restore optimal ICM memory allocation
Date: Fri, 1 Jun 2018 05:57:42 -0400	[thread overview]
Message-ID: <42473b16-e9c0-f556-4538-e4c47b2b1f1e@gmail.com> (raw)
In-Reply-To: <d470065c-f45d-7761-b347-729fb49c89c9@oracle.com>



On 05/31/2018 09:51 PM, Qing Huang wrote:
> 

> It would be great if you could share the test case that triggered the KASAN report in your
> environment. Our QA has been running intensive tests using 8KB or 4KB chunk size configuration
> for some time, no one has reported memory corruption issues so far, given that we are not
> running the latest upstream kernel.
> 
> IMO, it's worthwhile to find out the root cause and fix the problem.
> 

Do not worry, we are working on this minor problem.

We do not use KASAN on production hosts, quite obviously.

The memory waste is the major problem really.

  reply	other threads:[~2018-06-01  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 12:52 [PATCH v2 net] mlx4_core: restore optimal ICM memory allocation Eric Dumazet
2018-06-01  1:51 ` Qing Huang
2018-06-01  9:57   ` Eric Dumazet [this message]
2018-06-03 15:02 ` 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=42473b16-e9c0-f556-4538-e4c47b2b1f1e@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=danielj@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jsperbeck@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=qing.huang@oracle.com \
    --cc=tarick@google.com \
    --cc=yanjun.zhu@oracle.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.