From: Bart Van Assche <bvanassche@acm.org>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>
Cc: "target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"'linux-rdma@vger.kernel.org'" <linux-rdma@vger.kernel.org>
Subject: Re: Recent trace observed in target code during iSer testing
Date: Fri, 17 Jan 2020 08:35:04 -0800 [thread overview]
Message-ID: <a686b847-846e-1495-a7ff-d6184631e296@acm.org> (raw)
In-Reply-To: <MWHPR1101MB227156761E41FA7C47DAE5A486310@MWHPR1101MB2271.namprd11.prod.outlook.com>
On 1/17/20 7:55 AM, Marciniszyn, Mike wrote:
>> Subject: RE: Recent trace observed in target code during iSer testing
>>
>>>
>>> A candidate fix has been posted but needs review and/or a Tested-by. See
>>> also https://www.spinics.net/lists/target-devel/msg17981.html.
>>>
>>> Thanks,
>>>
>>> Bart.
>>
>> I'm testing this now.
>>
>
> I have tested this change an it certainly eliminates the percpu message.
>
> Have you submitted a patch? I actually extracted the patch from the email thread.
>
> When you do feel free to add:
> Tested-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
Thanks Mike for having tested this patch. The patch itself has been
cross-posted to the target-devel and linux-rdma mailing lists. See also
https://lore.kernel.org/linux-rdma/20200116044737.19507-1-bvanassche@acm.org/
Bart.
prev parent reply other threads:[~2020-01-17 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 18:23 Recent trace observed in target code during iSer testing Marciniszyn, Mike
2020-01-07 2:56 ` Bart Van Assche
2020-01-08 16:18 ` Marciniszyn, Mike
2020-01-17 15:55 ` Marciniszyn, Mike
2020-01-17 16:35 ` Bart Van Assche [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=a686b847-846e-1495-a7ff-d6184631e296@acm.org \
--to=bvanassche@acm.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=target-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).