From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Fabien Dessenne <fabien.dessenne@st.com>,
Jean-Christophe Trotin <jean-christophe.trotin@st.com>,
Yasunari Takiguchi <Yasunari.Takiguchi@sony.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: Are media drivers abusing of GFP_DMA? - was: Re: [LSF/MM TOPIC NOTES] x86 ZONE_DMA love
Date: Mon, 7 May 2018 12:19:16 -0300 [thread overview]
Message-ID: <20180507121916.4eb7f5b2@vento.lan> (raw)
In-Reply-To: <3561479.qPIcrWnXEC@avalon>
Em Mon, 07 May 2018 16:26:08 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> On Saturday, 5 May 2018 19:08:15 EEST Mauro Carvalho Chehab wrote:
> > There was a recent discussion about the use/abuse of GFP_DMA flag when
> > allocating memories at LSF/MM 2018 (see Luis notes enclosed).
> >
> > The idea seems to be to remove it, using CMA instead. Before doing that,
> > better to check if what we have on media is are valid use cases for it, or
> > if it is there just due to some misunderstanding (or because it was
> > copied from some other code).
> >
> > Hans de Goede sent us today a patch stopping abuse at gspca, and I'm
> > also posting today two other patches meant to stop abuse of it on USB
> > drivers. Still, there are 4 platform drivers using it:
> >
> > $ git grep -l -E "GFP_DMA\\b" drivers/media/
> > drivers/media/platform/omap3isp/ispstat.c
> > drivers/media/platform/sti/bdisp/bdisp-hw.c
> > drivers/media/platform/sti/hva/hva-mem.c
> > drivers/media/spi/cxd2880-spi.c
> >
> > Could you please check if GFP_DMA is really needed there, or if it is
> > just because of some cut-and-paste from some other place?
>
> I started looking at that for the omap3isp driver but Sakari beat me at
> submitting a patch. GFP_DMA isn't needed for omap3isp.
>
Thank you both for looking into it.
Regards,
Mauro
Thanks,
Mauro
next prev parent reply other threads:[~2018-05-07 15:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:54 [LSF/MM TOPIC NOTES] x86 ZONE_DMA love Luis R. Rodriguez
2018-04-27 1:09 ` [Lsf-pc] " Rik van Riel
2018-04-27 5:35 ` Christoph Hellwig
2018-04-27 7:18 ` Michal Hocko
2018-04-27 16:07 ` Christopher Lameter
2018-04-27 16:18 ` Matthew Wilcox
2018-04-27 16:36 ` Christopher Lameter
2018-04-28 8:33 ` Christoph Hellwig
2018-04-27 16:37 ` Michal Hocko
2018-04-28 8:33 ` Christoph Hellwig
2018-04-28 8:30 ` Christoph Hellwig
2018-04-27 16:14 ` Luis R. Rodriguez
2018-04-27 16:28 ` Matthew Wilcox
2018-04-28 8:42 ` Christoph Hellwig
2018-04-28 18:55 ` Luis R. Rodriguez
2018-04-28 19:10 ` Matthew Wilcox
2018-05-03 12:03 ` Michal Hocko
2018-05-03 12:13 ` Christoph Hellwig
2018-04-28 19:46 ` Julia Lawall
2018-04-28 20:41 ` Matthew Wilcox
2018-04-29 14:34 ` Julia Lawall
2018-05-03 8:20 ` Geert Uytterhoeven
2018-05-05 16:08 ` Are media drivers abusing of GFP_DMA? - was: " Mauro Carvalho Chehab
2018-05-07 13:26 ` Laurent Pinchart
2018-05-07 15:19 ` Mauro Carvalho Chehab [this message]
2018-05-14 8:00 ` Fabien DESSENNE
2018-05-14 10:35 ` Mauro Carvalho Chehab
2018-05-14 10:39 ` Mauro Carvalho Chehab
2018-05-15 7:30 ` Fabien DESSENNE
2018-05-15 8:27 ` Laurent Pinchart
2018-05-15 10:30 ` Mauro Carvalho Chehab
2018-05-15 16:24 ` Luis R. Rodriguez
2018-05-10 4:39 ` Yasunari.Takiguchi
2018-05-10 4:39 ` Yasunari.Takiguchi
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=20180507121916.4eb7f5b2@vento.lan \
--to=mchehab+samsung@kernel.org \
--cc=Yasunari.Takiguchi@sony.com \
--cc=fabien.dessenne@st.com \
--cc=jean-christophe.trotin@st.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=sakari.ailus@linux.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.