linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, hch@lst.de,
	cl@linux.com, John.p.donnelly@oracle.com,
	kexec@lists.infradead.org
Subject: Re: [PATCH v3 0/5] Avoid requesting page from DMA zone when no managed pages
Date: Tue, 14 Dec 2021 08:35:19 +0800	[thread overview]
Message-ID: <20211214003519.GA2216@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20211213130534.af47c7956c219797e6b56687@linux-foundation.org>

On 12/13/21 at 01:05pm, Andrew Morton wrote:
> On Mon, 13 Dec 2021 20:27:07 +0800 Baoquan He <bhe@redhat.com> wrote:
> 
> > Background information can be checked in cover letter of v2 RESEND POST
> > as below:
> > https://lore.kernel.org/all/20211207030750.30824-1-bhe@redhat.com/T/#u
> 
> Please include all relevant info right here, in the [0/n].  For a
> number of reasons, one of which is that the text is more likely to be
> up to date as the patchset evolves.
> 
> It's unusual that this patchset has two non-urgent patches and the
> final three patches are cc:stable.  It makes one worry that patches 3-5
> might have dependencies on 1-2.  Also, I'd expect to merge the three
> -stable patches during 5.16-rcX which means I have to reorder things,
> redo changelogs, update links and blah blah.
> 
> So can I ask that you redo all of this as two patch series?  A 3-patch
> series which is targeted at -stable, followed by a separate two-patch
> series which is targeted at 5.17-rc1.  Each series with its own fully
> prepared [0/n] cover.

Sure, will do. Sorry for the mess.

Before the 3-patch series posting, I may need to continue discussing and
making clear if the current patch 5/5 is a good fix, or whether we need
change to take other solution. So I will take the first two patches out
and post them.



      reply	other threads:[~2021-12-14  0:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 12:27 [PATCH v3 0/5] Avoid requesting page from DMA zone when no managed pages Baoquan He
2021-12-13 12:27 ` [PATCH v3 1/5] docs: kernel-parameters: Update to reflect the current default size of atomic pool Baoquan He
2021-12-13 14:20   ` john.p.donnelly
2021-12-13 12:27 ` [PATCH v3 2/5] dma-pool: allow user to disable " Baoquan He
2021-12-13 14:21   ` john.p.donnelly
2021-12-13 12:27 ` [PATCH v3 3/5] mm_zone: add function to check if managed dma zone exists Baoquan He
2021-12-13 14:22   ` john.p.donnelly
2021-12-16 10:52   ` David Hildenbrand
2021-12-13 12:27 ` [PATCH v3 4/5] dma/pool: create dma atomic pool only if dma zone has managed pages Baoquan He
2021-12-13 14:23   ` john.p.donnelly
2021-12-13 12:27 ` [PATCH v3 5/5] mm/slub: do not create dma-kmalloc if no managed pages in DMA zone Baoquan He
2021-12-13 13:43   ` Hyeonggon Yoo
2021-12-14  5:32     ` Baoquan He
2021-12-14 10:09       ` Vlastimil Babka
2021-12-14 10:28         ` Christoph Lameter
2021-12-15  4:48         ` Hyeonggon Yoo
     [not found]           ` <20211215070335.GA1165926@odroid>
2021-12-15  7:27             ` Christoph Hellwig
2021-12-15 10:34               ` Vlastimil Babka
2021-12-15 11:51                 ` David Laight
2021-12-15 13:41                 ` Baoquan He
2021-12-17 11:38               ` Hyeonggon Yoo
2021-12-20  7:32                 ` Baoquan He
2021-12-15 14:42             ` Baoquan He
2021-12-15 10:08         ` Baoquan He
2021-12-17 11:38       ` Hyeonggon Yoo
2021-12-21  8:56         ` Christoph Hellwig
2021-12-22 12:37           ` Hyeonggon Yoo
2021-12-23  8:52             ` Christoph Hellwig
2021-12-13 14:24   ` john.p.donnelly
2021-12-14 16:31   ` Christoph Hellwig
2021-12-14 17:07     ` john.p.donnelly
2021-12-15  7:27       ` Christoph Hellwig
2021-12-13 21:05 ` [PATCH v3 0/5] Avoid requesting page from DMA zone when no managed pages Andrew Morton
2021-12-14  0:35   ` Baoquan He [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=20211214003519.GA2216@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=John.p.donnelly@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=hch@lst.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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;
as well as URLs for NNTP newsgroup(s).