From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: "leon-2ukJVAZIZ/Y@public.gmane.org" <leon-2ukJVAZIZ/Y@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Nicholas A. Bellinger"
<nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH for kernel v4.6] IB/srpt: Revert "Convert to percpu_ida tag allocation"
Date: Thu, 31 Mar 2016 20:12:57 -0700 [thread overview]
Message-ID: <56FDE739.9090801@sandisk.com> (raw)
In-Reply-To: <20160401030322.GH2670-2ukJVAZIZ/Y@public.gmane.org>
On 03/31/16 20:05, Leon Romanovsky wrote:
> On Thu, Mar 31, 2016 at 05:01:39PM -0700, Bart Van Assche wrote:
>> That patch is wrong because it makes the ib_srpt driver use I/O
>> contexts allocated by transport_alloc_session_tags() but it does
>> not initialize these I/O contexts properly.
>
> Did you have a chance to see which initializations are missing in this
> case? What is needed to do if we decide to fix original patch?
>
> Except these questions, the revert is fine :)
> Reviewed-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Hello Leon,
Thanks for the review. The initializations that are missing from that
patch are the 'buf' pointer in the srpt_ioctx structure and mapping that
buffer for DMA. Another bug introduced by that patch is that it doubles
the amount of memory that is allocated for I/O contexts. New I/O context
allocations were added by that patch but the existing I/O context
allocation code was not removed.
Regarding reconsidering the original patch: before we do that it has to
be shown with numbers that the percpu_ida conversion does not decrease
performance. This is something I had already asked two months ago. See
also
http://thread.gmane.org/gmane.linux.scsi.target.devel/11253/focus=110559.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-01 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:01 [PATCH for kernel v4.6] IB/srpt: Revert "Convert to percpu_ida tag allocation" Bart Van Assche
[not found] ` <56FDBA63.7010804-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-04-01 3:03 ` Leon Romanovsky
[not found] ` <20160401030322.GH2670-2ukJVAZIZ/Y@public.gmane.org>
2016-04-01 3:12 ` Bart Van Assche [this message]
[not found] ` <56FDE739.9090801-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-04-01 3:45 ` leon-2ukJVAZIZ/Y
2016-04-03 3:56 ` Nicholas A. Bellinger
[not found] ` <1459655763.13184.45.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2016-04-03 13:13 ` sagig
[not found] ` <570116E0.3010401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-04 18:34 ` Nicholas A. Bellinger
2016-04-03 14:26 ` Bart Van Assche
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=56FDE739.9090801@sandisk.com \
--to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=leon-2ukJVAZIZ/Y@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.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).