All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Herranz <albert_herranz@yahoo.es>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC
Date: Tue, 16 Mar 2010 06:17:46 +0000	[thread overview]
Message-ID: <4B9F228A.8030005@yahoo.es> (raw)
In-Reply-To: <20100316112444D.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
> If we want to make swiotlb generic (make on any architectures), we
> need to handle more cache issues here, I think. So it's better to have
> more generic ways instead of adding hooks to some archs.
> 

Ok. So what would be an acceptable way of handling this in a generic way?
Should we for example have 2 levels of DMA ops in the swiotlb case (swiotlb and "actual") and call the 2nd level ("actual") from the swiotlb code whenever we need to act on non-bounced buffers?
Any other ideas?

Thanks,
Albert


WARNING: multiple messages have this Message-ID (diff)
From: Albert Herranz <albert_herranz@yahoo.es>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: x86@kernel.org, linux-ia64@vger.kernel.org,
	linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms
Date: Tue, 16 Mar 2010 07:17:46 +0100	[thread overview]
Message-ID: <4B9F228A.8030005@yahoo.es> (raw)
In-Reply-To: <20100316112444D.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
> If we want to make swiotlb generic (make on any architectures), we
> need to handle more cache issues here, I think. So it's better to have
> more generic ways instead of adding hooks to some archs.
> 

Ok. So what would be an acceptable way of handling this in a generic way?
Should we for example have 2 levels of DMA ops in the swiotlb case (swiotlb and "actual") and call the 2nd level ("actual") from the swiotlb code whenever we need to act on non-bounced buffers?
Any other ideas?

Thanks,
Albert

WARNING: multiple messages have this Message-ID (diff)
From: Albert Herranz <albert_herranz@yahoo.es>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms
Date: Tue, 16 Mar 2010 07:17:46 +0100	[thread overview]
Message-ID: <4B9F228A.8030005@yahoo.es> (raw)
In-Reply-To: <20100316112444D.fujita.tomonori@lab.ntt.co.jp>

FUJITA Tomonori wrote:
> If we want to make swiotlb generic (make on any architectures), we
> need to handle more cache issues here, I think. So it's better to have
> more generic ways instead of adding hooks to some archs.
> 

Ok. So what would be an acceptable way of handling this in a generic way?
Should we for example have 2 levels of DMA ops in the swiotlb case (swiotlb and "actual") and call the 2nd level ("actual") from the swiotlb code whenever we need to act on non-bounced buffers?
Any other ideas?

Thanks,
Albert


  reply	other threads:[~2010-03-16  6:17 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 19:12 [PATCH v4 00/11] wii: add usb 2.0 support Albert Herranz
2010-03-12 19:12 ` [PATCH v4 01/11] powerpc: add per-device dma coherent support Albert Herranz
2010-03-12 19:12 ` [PATCH v4 02/11] powerpc: add min_direct_dma_addr Albert Herranz
2010-03-12 19:12 ` [PATCH v4 03/11] swiotbl: add back swiotlb_alloc_boot() Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-12 19:12 ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-16  1:54   ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC FUJITA Tomonori
2010-03-16  1:54     ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms FUJITA Tomonori
2010-03-16  1:54     ` FUJITA Tomonori
2010-03-16  2:25     ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC FUJITA Tomonori
2010-03-16  2:25       ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms FUJITA Tomonori
2010-03-16  2:25       ` FUJITA Tomonori
2010-03-16  6:17       ` Albert Herranz [this message]
2010-03-16  6:17         ` Albert Herranz
2010-03-16  6:17         ` Albert Herranz
2010-03-16  6:09     ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC Albert Herranz
2010-03-16  6:09       ` [PATCH v4 04/11] swiotlb: support NOT_COHERENT_CACHE PowerPC platforms Albert Herranz
2010-03-16  6:09       ` Albert Herranz
2010-03-12 19:12 ` [PATCH v4 05/11] swiotlb: add swiotlb_set_default_size() Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-12 19:12   ` Albert Herranz
2010-03-16  1:44   ` FUJITA Tomonori
2010-03-16  1:44     ` FUJITA Tomonori
2010-03-16  1:44     ` FUJITA Tomonori
2010-03-16  5:58     ` Albert Herranz
2010-03-16  5:58       ` Albert Herranz
2010-03-16  5:58       ` Albert Herranz
2010-03-16 10:08       ` FUJITA Tomonori
2010-03-16 10:08         ` FUJITA Tomonori
2010-03-16 10:08         ` FUJITA Tomonori
2010-03-16 19:28         ` Becky Bruce
2010-03-16 19:28           ` Becky Bruce
2010-03-16 19:28           ` Becky Bruce
2010-03-16 23:16           ` FUJITA Tomonori
2010-03-16 23:16             ` FUJITA Tomonori
2010-03-16 23:16             ` FUJITA Tomonori
2010-03-12 19:12 ` [PATCH v4 06/11] USB: refactor unmap_urb_for_dma/map_urb_for_dma Albert Herranz
2010-03-12 19:12 ` [PATCH v4 07/11] USB: add HCD_NO_COHERENT_MEM host controller driver flag Albert Herranz
2010-03-12 19:12 ` [PATCH v4 08/11] wii: have generic dma coherent Albert Herranz
2010-03-12 19:12 ` [PATCH v4 09/11] wii: add mem2 dma mapping ops Albert Herranz
2010-03-12 19:12 ` [PATCH v4 10/11] wii: enable swiotlb Albert Herranz
2010-03-12 19:12 ` [PATCH v4 11/11] wii: hollywood ehci controller support Albert Herranz

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=4B9F228A.8030005@yahoo.es \
    --to=albert_herranz@yahoo.es \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=x86@kernel.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 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.