From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"jiweisun126@126.com" <jiweisun126@126.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"ahuang12@lenovo.com" <ahuang12@lenovo.com>,
"sunjw10@lenovo.com" <sunjw10@lenovo.com>
Subject: Re: [PATCH] nvme: add cond_resched() to nvme_complete_batch()
Date: Thu, 4 May 2023 15:18:12 +0000 [thread overview]
Message-ID: <ZFPMs6e2c3tM99o0@x1-carbon> (raw)
In-Reply-To: <ZFPJ7CYFEextnOqE@kbusch-mbp.dhcp.thefacebook.com>
On Thu, May 04, 2023 at 09:06:20AM -0600, Keith Busch wrote:
> On Thu, May 04, 2023 at 10:12:46AM +0000, Niklas Cassel wrote:
> > On Thu, May 04, 2023 at 11:39:53AM +0200, Niklas Cassel wrote:
> > >
> > > Something is fishy here...
> > >
> > > (Perhaps the maintainer did a git revert instead of applying the fix...
> > > and accidentally squashed the revert with a proper commit...
> > > But even that does not make sense, as there simply seems to be too many
> > > lines changed in 2d55c16c0c54 ("dmapool: create/destroy cleanup") for that
> > > to be the case...)
> >
> > It seems like the additional lines in
> > 2d55c16c0c54 ("dmapool: create/destroy cleanup") is explained by the
> > maintainer (probably accidentally) reverting additional patches in that
> > very same commit.
> >
> > It seems like that commit reverted all changes to mm/dmapool.c since v6.3:
>
> Spot on, thanks for confirming! Somehow a series revert was squahed into
> the final patch. :(
>
> We reached the same conclusion pretty late yesterday, so I'll wait for
> Andrew to suggest how to proceed. I think we have to rebase whole series
> with the correct final patch and resend the pull.
>
> > $ git log --oneline 2d55c16c0c54325bf15286cfa6ba6c268036b9e4 --not v6.3 mm/dmapool.c
> > 2d55c16c0c54 dmapool: create/destroy cleanup
> > a4de12a032fa dmapool: link blocks across pages
> > 9d062a8a4c6d dmapool: don't memset on free twice
> > 887aef615818 dmapool: simplify freeing
> > 2591b516533b dmapool: consolidate page initialization
> > 36d1a28921a4 dmapool: rearrange page alloc failure handling
> > 52e7d5653979 dmapool: move debug code to own functions
> > 19f504584038 dmapool: speedup DMAPOOL_DEBUG with init_on_alloc
> > 347e4e44c0a9 dmapool: cleanup integer types
> > 65216545436b dmapool: use sysfs_emit() instead of scnprintf()
> > 7f796d141c07 dmapool: remove checks for dev == NULL
Hello Keith, Andrew,
Note that the first four patches were not part of Keith's series,
but they were reverted as well.
> Andrew actually squashed that fix into the original patch.
Ok, strange why there was a revert done at all then.
Kind regards,
Niklas
next prev parent reply other threads:[~2023-05-04 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 12:54 [PATCH] nvme: add cond_resched() to nvme_complete_batch() jiweisun126
2023-05-03 16:07 ` Christoph Hellwig
2023-05-03 16:28 ` Keith Busch
2023-05-03 23:42 ` Keith Busch
2023-05-04 9:39 ` Niklas Cassel
2023-05-04 10:12 ` Niklas Cassel
2023-05-04 15:06 ` Keith Busch
2023-05-04 15:18 ` Niklas Cassel [this message]
2023-05-15 20:40 ` Keith Busch
2023-05-16 13:58 ` Jiwei Sun
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=ZFPMs6e2c3tM99o0@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=ahuang12@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jiweisun126@126.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sunjw10@lenovo.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.