From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme/pci: Fix HMB size calculation
Date: Tue, 18 Jul 2017 14:04:32 -0400 [thread overview]
Message-ID: <20170718180431.GB7613@localhost.localdomain> (raw)
In-Reply-To: <20170718173954.GA7511@lst.de>
On Tue, Jul 18, 2017@07:39:54PM +0200, Christoph Hellwig wrote:
> On Mon, Jul 17, 2017@07:45:39PM -0400, Keith Busch wrote:
> > It's possible the preferred HMB size may not be a multiple of the
> > chunk_size. This patch will set the chunk_size to the descriptor's actual
> > length so the last iteration doesn't cause the total size to exceed the
> > allocated HMB size.
>
> This looks a little weird, and might do the wrong thing
> if we hit the retry loop after reducing chunk_size.
It may look weird when you consider the retry, but I'm pretty sure it
isn't wrong. The only way you can get to the retry is if the for-loop
breaks before the last interation, which means chunk_size will be
unchanged. That's not immediately obvious, though, so maybe this
implementation was trying to be too clever.
> I suspect we just need to change to
>
> for (size = 0; size < preferred; size += len) {
>
> and move len to function scope.
That's fine too.
prev parent reply other threads:[~2017-07-18 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 23:45 [PATCH] nvme/pci: Fix HMB size calculation Keith Busch
2017-07-17 23:47 ` Keith Busch
2017-07-18 17:39 ` Christoph Hellwig
2017-07-18 18:04 ` Keith Busch [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=20170718180431.GB7613@localhost.localdomain \
--to=keith.busch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.