mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	"hch@lst.de" <hch@lst.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>
Subject: Re: [RFC] ARC: allow to use IOC and non-IOC DMA devices simultaneously
Date: Mon, 25 Jun 2018 15:45:40 +0000	[thread overview]
Message-ID: <456ab2264aa42d575e7ca5d28d34466aea082f14.camel@synopsys.com> (raw)
In-Reply-To: <1529677805.31605.28.camel@synopsys.com>

Hi Eugeniy,

On Fri, 2018-06-22 at 16:30 +0200, Eugeniy Paltsev wrote:
> Hi Vineet, Christoph,
> thanks for responding.

[snip]

> > > (BTW: current ARC dma_noncoherent_ops implementation also has same
> > > problem if IOC and HIGHMEM are enabled.)
> > 
> > Can we highlight this fact, add error prints somewhere ?
> 
> The easiest solution is to panic if both IOC and ZONE_HIGHMEM enabled.

I don't think it's the best idea - I would expect to get PAE40 enabled
by default or at least to be used quite often on both AXS103 and HSDK
and so restricting usage of IOC on such configurations will be quite
confusing.

That said we need to figure out how to get IOC + HIGHMEM/PAE working
reliably if that's possible at all.

Christoph, do you think if this is doable?
The main concern here is: some random data buffer might be allocated
in any available memory [and in HIGHMEM/PAE if it exists essentially] and
when it comes to DMA exchange that involves that buffer what should we do?

The only thing I may think of could be a bounce-buffer in ZONE_NORMAL.
Is it used by anybody? Are there any better ideas? 

-Alexey

      reply	other threads:[~2018-06-25 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 12:58 Eugeniy Paltsev
2018-06-15 13:17 ` Christoph Hellwig
2018-06-18 22:53 ` Vineet Gupta
2018-06-22 14:30   ` Eugeniy Paltsev
2018-06-25 15:45     ` Alexey Brodkin [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=456ab2264aa42d575e7ca5d28d34466aea082f14.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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

all inboxes | Powered by JetHome®