From: Bart.VanAssche@sandisk.com (Bart Van Assche)
Subject: [PATCH v4, under testing] nvme-rdma: support devices with queue size < 32
Date: Wed, 3 May 2017 16:24:00 +0000 [thread overview]
Message-ID: <1493828639.3901.11.camel@sandisk.com> (raw)
In-Reply-To: <92010426-c898-0a56-e615-bbf6eb1c5e7e@redhat.com>
On Wed, 2017-05-03@12:17 -0400, Doug Ledford wrote:
> On 5/3/2017 11:58 AM, Bart Van Assche wrote:
> > On Wed, 2017-05-03@09:53 -0600, Jason Gunthorpe wrote:
> > > On Wed, May 03, 2017@05:19:27PM +0200, Marta Rybczynska wrote:
> > >
> > > > > where
> > > > > queue->sig_limit = max(queue->queue_size / 2, 1);
> > > >
> > > > I tried to avoid that because this adds a division in the fast path Bart
> > > > was unhappy about in v2.
> > >
> > > The compiler switches divide/multiply by powers of two into fast bit shifts.
> >
> > Hello Jason,
> >
> > As far as I know the compiler only does that for compile-time constants. In
> > this case the divisor (max(queue_size / 2, 1)) is not a compile-time constant.
>
> Sure it is. The only thing that needs to be constant for the compiler
> to do the right thing is the '/ 2' part. queue_size need not be
> constant, and the max is performed after the division. I would fully
> expect the compiler to get this right and convert it internally to the
> equivalent bit shift, but if it didn't you could always just write it
> that way in the first place:
>
> queue->sig_limit = max(queue->queue_size >> 1, 1);
Hello Doug,
In my comment I was referring to "% max(queue_size / 2, 1)" and not to
"queue_size / 2".
Bart.
next prev parent reply other threads:[~2017-05-03 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:05 [PATCH v4, under testing] nvme-rdma: support devices with queue size < 32 Marta Rybczynska
2017-05-03 11:17 ` Leon Romanovsky
2017-05-03 15:08 ` Sagi Grimberg
2017-05-03 15:19 ` Marta Rybczynska
2017-05-03 15:45 ` Bart Van Assche
2017-05-03 15:53 ` Jason Gunthorpe
2017-05-03 15:58 ` Bart Van Assche
2017-05-03 16:01 ` Sagi Grimberg
2017-05-03 16:27 ` Leon Romanovsky
2017-05-03 16:37 ` Bart Van Assche
2017-05-03 16:49 ` Sagi Grimberg
2017-05-04 12:50 ` Marta Rybczynska
2017-05-17 9:02 ` Christoph Hellwig
2017-05-17 12:50 ` Marta Rybczynska
2017-05-03 16:17 ` Doug Ledford
2017-05-03 16:24 ` Bart Van Assche [this message]
2017-05-03 19:07 ` Doug Ledford
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=1493828639.3901.11.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
/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