Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Gladkov <Victor.Gladkov@kioxia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [bug report] nvmet-tcp: Memory leak when connecting / disconnecting to the target
Date: Mon, 1 Jun 2020 15:28:00 +0000	[thread overview]
Message-ID: <d9e18f6916a24a5a921ebbf5ec5e0249@kioxia.com> (raw)

[Environment]
Branch: nvme-5.7
Commit: 9210c075cef29c1f764b4252f93105103bdfb292

[Steps]
At the target:
1.1 Check free memory before the test
	# grep MemFree /proc/meminfo
	MemFree:        64060460 kB
1.2 Create portal:
	#./target_create_portal.sh 1 69.69.69.1 4420 tcp
1.3 Create target:
	#./target_add.sh /dev/nvme1n1 target_t0 1

At the host:
2.1 Connect to the target (number of IO queues is 10)
2.2 Disconnect from the target.
2.3 Repeat steps 2.1 and 2.2 ~1000 times

At the target:
3.1 Check free memory after the test
	# grep MemFree /proc/meminfo
	MemFree:        63685072 kB 

[Result]:
Free memory of the target system was reduce to 375388 kB
Note: The size of leakage memory depends on the number of IO queues.

Best Regards,
Victor Gladkov


_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2020-06-01 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 15:28 Victor Gladkov [this message]
2020-06-02  7:26 ` [bug report] nvmet-tcp: Memory leak when connecting / disconnecting to the target Sagi Grimberg
2020-06-02  9:14   ` Victor Gladkov

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=d9e18f6916a24a5a921ebbf5ec5e0249@kioxia.com \
    --to=victor.gladkov@kioxia.com \
    --cc=linux-nvme@lists.infradead.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