From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"jthumshirn@suse.de" <jthumshirn@suse.de>
Subject: Re: [PATCH] nvmet: Always remove processed AER elements from list
Date: Mon, 4 Nov 2019 20:41:00 +0000 [thread overview]
Message-ID: <BYAPR04MB574938B5AF804C910EDE4A6E867F0@BYAPR04MB5749.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20191104081338.gdrk2a4mlov2io6s@beryllium.lan
On 11/04/2019 12:13 AM, Daniel Wagner wrote:
>> >I did the basic testing create/delete ctrl and enable/disable ns that
>> >did not produced any hands or errors.
> Thanks for addressing Christoph's comment. I'll get this patch into
> our customer's test setup.
>
>> >Following is the test log if anyone wants to take a look:-
>> # echo 0 > /sys/kernel/config/nvmet/subsystems/fs/namespaces/1/enable
>> ># nvme list | tr -s ' ' ' ' | grep Linux | grep -v '\-\-\-\-'
>> ># echo 1 > /sys/kernel/config/nvmet/subsystems/fs/namespaces/1/enable
> BTW, I got feedback how to produce the oops on our custerms setup:
>
You are welcome.
> Test Steps:
> 1. Create two targets on node n1 as target side (tgt1 and tgt2)
> 2. Run perf to write data to tgt2:
> sudo ./perf -q 1 -w read -o 4096 -t 60 -r 'trtype:RDMA adrfam:IPv4 traddr:192.168.219.4 trsvcid:4421'
> 3. Deleted tgt2 node n1 configuration during perf execution
> and reboot the node n1 automatically.
>
> I hope I got the steps summerized correctly.
>
Interesting let me have a look at this later this week.
> Thanks,
> Daniel
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-11-04 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 20:13 [PATCH] nvmet: Always remove processed AER elements from list Chaitanya Kulkarni
2019-11-04 8:13 ` Daniel Wagner
2019-11-04 9:50 ` Johannes Thumshirn
2019-11-04 10:19 ` Daniel Wagner
2019-11-08 10:42 ` Daniel Wagner
2019-11-10 2:25 ` Chaitanya Kulkarni
2019-11-11 7:28 ` Daniel Wagner
2019-12-05 9:23 ` Daniel Wagner
2019-12-11 7:39 ` Chaitanya Kulkarni
2019-12-12 9:35 ` hch
2019-11-04 20:41 ` Chaitanya Kulkarni [this message]
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=BYAPR04MB574938B5AF804C910EDE4A6E867F0@BYAPR04MB5749.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=dwagner@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).