From: Max Gurtovoy <maxg@mellanox.com>
To: Doug Ledford <dledford@redhat.com>,
Bart Van Assche <bart.vanassche@wdc.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Sagi Grimberg <sagi@grimberg.me>
Cc: Chuck Lever <chuck.lever@oracle.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"leonro@mellanox.com" <leonro@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] RDMA/core: reduce IB_POLL_BATCH constant
Date: Thu, 1 Mar 2018 11:36:50 +0200 [thread overview]
Message-ID: <efc0302c-90e2-2e09-7525-dc9b9e247e73@mellanox.com> (raw)
In-Reply-To: <1519844114.28560.216.camel@redhat.com>
On 2/28/2018 8:55 PM, Doug Ledford wrote:
> On Wed, 2018-02-28 at 11:50 +0200, Max Gurtovoy wrote:
>>
>> On 2/28/2018 2:21 AM, Bart Van Assche wrote:
>>> On 02/27/18 14:15, Max Gurtovoy wrote:
>>>> -static int __ib_process_cq(struct ib_cq *cq, int budget, struct ib_wc
>>>> *poll_wc)
>>>> +static int __ib_process_cq(struct ib_cq *cq, int budget, struct ib_wc
>>>> *poll_wc,
>>>> + int batch)
>>>> {
>>>> - int i, n, completed = 0;
>>>> - struct ib_wc *wcs = poll_wc ? : cq->wc;
>>>> + int i, n, ib_poll_batch, completed = 0;
>>>> + struct ib_wc *wcs;
>>>> +
>>>> + if (poll_wc) {
>>>> + wcs = poll_wc;
>>>> + ib_poll_batch = batch;
>>>> + } else {
>>>> + wcs = cq->wc;
>>>> + ib_poll_batch = IB_POLL_BATCH;
>>>> + }
>>>
>>> Since this code has to be touched I think that we can use this
>>> opportunity to get rid of the "poll_wc ? : cq->wc" conditional and
>>> instead use what the caller passes. That will require to update all
>>> __ib_process_cq(..., ..., NULL) calls. I also propose to let the caller
>>> pass ib_poll_batch instead of figuring it out in this function.
>>> Otherwise the approach of this patch looks fine to me.
>>
>> Thanks Bart.
>> I'll make these changes and submit.
>
> That sounds reasonable to me too, thanks for reworking and resubmitting.
>
Sure, NP.
We've run NVMe-oF and SRP with the new patch.
I'll send it through Mellanox maintainers pull request.
Thanks for reporting and reviewing.
-Max.
next prev parent reply other threads:[~2018-03-01 9:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 20:59 Arnd Bergmann
2018-02-20 21:14 ` Parav Pandit
2018-02-20 21:54 ` Arnd Bergmann
2018-02-20 21:14 ` Bart Van Assche
2018-02-20 21:47 ` Chuck Lever
2018-02-21 9:47 ` Max Gurtovoy
2018-02-21 13:44 ` Sagi Grimberg
2018-02-21 14:45 ` Max Gurtovoy
2018-02-22 15:39 ` Sagi Grimberg
2018-02-27 22:09 ` Jason Gunthorpe
2018-02-27 22:15 ` Max Gurtovoy
2018-02-28 0:21 ` Bart Van Assche
2018-02-28 9:50 ` Max Gurtovoy
2018-02-28 18:55 ` Doug Ledford
2018-03-01 9:36 ` Max Gurtovoy [this message]
2018-02-21 15:10 ` Chuck Lever
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=efc0302c-90e2-2e09-7525-dc9b9e247e73@mellanox.com \
--to=maxg@mellanox.com \
--cc=arnd@arndb.de \
--cc=bart.vanassche@wdc.com \
--cc=chuck.lever@oracle.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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
all inboxes | Powered by JetHome®