Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: leonro@mellanox.com (Leon Romanovsky)
Subject: [PATCH v4, under testing] nvme-rdma: support devices with queue size < 32
Date: Wed, 3 May 2017 19:27:08 +0300	[thread overview]
Message-ID: <20170503162708.GO22833@mtr-leonro.local> (raw)
In-Reply-To: <77ada146-67eb-9dce-d252-6ac630c9a1e8@grimberg.me>

On Wed, May 03, 2017@07:01:14PM +0300, Sagi Grimberg wrote:
>
> > 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.
>
> We could theoretically do a (sig_count & max(queue_size / 2, 1)) but
> that would only do well with power of 2 sized queues...

IMHO, It is not-so-big-deal limitation.

> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20170503/bb3a3888/attachment.sig>

  reply	other threads:[~2017-05-03 16:27 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 [this message]
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
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=20170503162708.GO22833@mtr-leonro.local \
    --to=leonro@mellanox.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