From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH] nvmet: Always remove processed AER elements from list
Date: Wed, 11 Dec 2019 07:39:08 +0000 [thread overview]
Message-ID: <BYAPR04MB5749A45B82AC14331E59E412865A0@BYAPR04MB5749.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20191205092357.q37ok6auxeyuvi23@beryllium.lan
Christoph/Sagi,
Should we get this patch in ?
On 12/05/2019 01:24 AM, Daniel Wagner wrote:
> Hi Chaitanya,
>
> On Sun, Nov 10, 2019 at 02:25:21AM +0000, Chaitanya Kulkarni wrote:
>> Did you see the same problem with the patch I've provided ?
>
> I don't have the hardware to test on. I was unable to reproduce it
> with TCP as transport and virtual machines. Unfortunatly, the
> customer decided to 'solve' this problem by removing the AER handling
> code in the SPDK stack and gave no feedback if this patch solves
> the problem or not.
>
> Since we can't really verify it I am not sure if you should pick the
> patch.
>
> Thanks,
> Daniel
>
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-11 7:39 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 [this message]
2019-12-12 9:35 ` hch
2019-11-04 20:41 ` Chaitanya Kulkarni
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=BYAPR04MB5749A45B82AC14331E59E412865A0@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).