> >Just pointing out that it's not clear it will always be a big help. > > > > > > > Agree it should default to in-cache. This would mean no DMA engine by default. Clearly there needs to be some heuristic to decide by default. We'll see how effective it will be in the end. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Andrew Grover <andrew.grover@intel.com>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Jeff Garzik <jgarzik@pobox.com>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Andi Kleen <ak@suse.de>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Benjamin LaHaise <bcrl@kvack.org>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Andi Kleen <ak@suse.de>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Avi Kivity <avi@argo.co.il>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Andi Kleen <ak@suse.de>
- Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- From: Avi Kivity <avi@argo.co.il>
- [RFC] [PATCH 0/3] ioat: DMA engine support
- Prev by Date: Re: [patch] SMP alternatives
- Next by Date: [PATCH] fbcon: fix obvious bug in fbcon logo rotation code
- Previous by thread: Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- Next by thread: Re: [RFC] [PATCH 0/3] ioat: DMA engine support
- Index(es):
 |