Messages in this thread | | | Date | Wed, 18 May 2005 15:28:49 +0100 | From | Christoph Hellwig <> | Subject | Re: [RFC/PATCH 4/5] loop: execute in place (V2) |
| |
On Wed, May 18, 2005 at 03:53:52PM +0200, Carsten Otte wrote: > [RFC/PATCH 4/5] loop: execute in place (V2) > The old loop driver in 2.6.11. used the readpage/writepage aops to > transfer data. Now loop can also use read/write and direct_IO on the > file if readpage/writepage are not available. Unlike the old 2.6.11. > version, today's loop driver does work with files that do not have > readpage/writepage. Threrefore, this patch is optional. > This patch adds one more transport method to loop that uses the new > address space operation get_xip_page if available. > > This patch is unchanged from previous version.
This should be ifdef'ed to avoid bloat for non-XIP builds. Or just be dropped completely. How much difference does it make over read/write and where does loop performance matter?
- 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/
| |