From: Carsten Otte <cotte@freenet.de>
To: suparna@in.ibm.com
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
schwidefsky@de.ibm.com, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC/PATCH 2/4] fs/mm: execute in place (3rd version)
Date: Thu, 26 May 2005 15:19:27 +0200 [thread overview]
Message-ID: <4295CCDF.9070302@freenet.de> (raw)
In-Reply-To: <20050526132251.GA5067@in.ibm.com>
Suparna Bhattacharya wrote:
> To get a complete picture, how did you want to handle direct io ?
>
>Regards
>Suparna
>
>
Just through the regular xip path, O_DIRECT doesn't have any effect
on those files since we do a direct memcpy to disk in the end anyway.
That has the user-visible effect that unalligned reads/writes work with
O_DIRECT.
next prev parent reply other threads:[~2005-05-26 13:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1116866094.12153.12.camel@cotte.boeblingen.de.ibm.com>
2005-05-23 17:30 ` [RFC/PATCH 2/4] fs/mm: execute in place (3rd version) Carsten Otte
2005-05-24 9:30 ` Suparna Bhattacharya
2005-05-24 10:28 ` Jörn Engel
2005-05-24 10:28 ` Jörn Engel
2005-05-24 11:09 ` Carsten Otte
2005-05-24 13:32 ` Suparna Bhattacharya
2005-05-24 14:34 ` Carsten Otte
2005-05-25 17:51 ` Badari Pulavarty
2005-05-26 13:22 ` Suparna Bhattacharya
2005-05-26 13:19 ` Carsten Otte [this message]
2005-05-26 16:43 ` Badari Pulavarty
2005-05-26 13:29 ` Carsten Otte
2005-05-28 9:05 ` Christoph Hellwig
2005-05-24 17:01 ` Carsten Otte
2005-05-28 9:08 ` Christoph Hellwig
2005-05-23 17:30 ` [RFC/PATCH 3/4] ext2: " Carsten Otte
2005-05-23 17:30 ` [RFC/PATCH 4/4] madvice/fadvice: " Carsten Otte
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=4295CCDF.9070302@freenet.de \
--to=cotte@freenet.de \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=suparna@in.ibm.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.