All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maurizio Lombardi <mlombard@redhat.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH RFC] nvmet: fix tmpfs-based backstores support
Date: Thu, 18 Nov 2021 09:29:28 +0100	[thread overview]
Message-ID: <20211118082928.GA82729@raketa> (raw)
In-Reply-To: <b0c0a83c-df9a-0a91-1dff-f6bc647a5b81@nvidia.com>

On Thu, Nov 18, 2021 at 01:59:29AM +0000, Chaitanya Kulkarni wrote:
> We will need blktests for this.
> 
> Also, can you share performance numbers with this patch and
> the errors that you are getting without this patch ?

Ok, I will try to run blktests and provide some performance numbers.

Without this patch, writes get lost:

[root@kvm-02-guest03 ~]# nvme connect -t tcp -a 10.37.153.75 -n test-nqn -s 4080
[root@kvm-02-guest03 ~]# dd if=/dev/urandom of=/dev/nvme0n1 bs=1M count=1
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0604551 s, 17.3 MB/s
[root@kvm-02-guest03 ~]# hexdump -C /dev/nvme0n1 
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
06400000

dmesg output:

[81489.687548] blk_update_request: critical target error, dev nvme0c0n1, sector 0 op 0x1:(WRITE) flags 0x2000800 phys_seg 256 prio class 0
[81489.691139] buffer_io_error: 246 callbacks suppressed
[81489.691141] Buffer I/O error on dev nvme0n1, logical block 0, lost async page write
[81489.695013] Buffer I/O error on dev nvme0n1, logical block 1, lost async page write
[81489.697183] Buffer I/O error on dev nvme0n1, logical block 2, lost async page write
[81489.699239] Buffer I/O error on dev nvme0n1, logical block 3, lost async page write
[81489.701297] Buffer I/O error on dev nvme0n1, logical block 4, lost async page write
[81489.703374] Buffer I/O error on dev nvme0n1, logical block 5, lost async page write
[81489.705459] Buffer I/O error on dev nvme0n1, logical block 6, lost async page write
[81489.707511] Buffer I/O error on dev nvme0n1, logical block 7, lost async page write
[81489.709438] Buffer I/O error on dev nvme0n1, logical block 8, lost async page write
[81489.711364] Buffer I/O error on dev nvme0n1, logical block 9, lost async page write

Maurizio



  reply	other threads:[~2021-11-18  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 15:24 [PATCH RFC] nvmet: fix tmpfs-based backstores support Maurizio Lombardi
2021-11-18  1:59 ` Chaitanya Kulkarni
2021-11-18  8:29   ` Maurizio Lombardi [this message]
2021-11-18  8:41     ` Chaitanya Kulkarni
2021-11-18  8:42     ` Chaitanya Kulkarni
2021-11-18  9:16       ` Maurizio Lombardi
2021-11-19 17:02 ` Christoph Hellwig
2021-11-21 14:25   ` Maurizio Lombardi

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=20211118082928.GA82729@raketa \
    --to=mlombard@redhat.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.