From: Baoquan He <bhe@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] sr: don't use GFP_DMA
Date: Thu, 23 Dec 2021 17:16:15 +0800 [thread overview]
Message-ID: <20211223091615.GC10050@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20211223090137.GB7555@lst.de>
On 12/23/21 at 10:01am, Christoph Hellwig wrote:
> On Wed, Dec 22, 2021 at 06:40:46PM +0800, Baoquan He wrote:
> > Any thought or plan for those callsites in other places? Possibly we can
> > skip those s390 related drivers since s390 only has DMA zone, no DMA32,
> > it should be OK.
>
> Yes, this needs a bit of an audit. A lot of them might be best handled
> by the subsysem maintainers, e.g. for crypto media and sound.
Yes, agree. I can send a mail to subsystem maintainers about this, ask
them for help.
>
> > And could you please also add me to CC when send out these patches? We
> > have this problem in our RHEL8 which is based on kernel4.18, if finally
> > removing dma-kmalloc(), we need back port these driver fixes too. If
> > not paying attention, these patches may scatter in different
> > sub-components and unnoticable.
>
> I already sent them out yesterday. Just look for everything with
> GFP_DMA in the subject line in the current scsi tree for 5.17.
Got, thx.
next prev parent reply other threads:[~2021-12-23 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 9:08 [PATCH v2] sr: don't use GFP_DMA Christoph Hellwig
2021-12-22 9:37 ` Baoquan He
2021-12-22 9:42 ` Christoph Hellwig
2021-12-22 10:40 ` Baoquan He
2021-12-23 9:01 ` Christoph Hellwig
2021-12-23 9:16 ` Baoquan He [this message]
2021-12-23 4:45 ` Martin K. Petersen
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=20211223091615.GC10050@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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