From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] 2.6 I/O path totally messed up
Date: Mon Aug 30 11:10:59 2004 [thread overview]
Message-ID: <20040830161052.GC15160@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20040830135022.GA17620@lst.de>
On Mon, Aug 30, 2004 at 03:50:22PM +0200, Christoph Hellwig wrote:
> The second argumentto generic_file_write_nolock is an iovec, not an
> actual userbuffer. The current code doesn't even have the slightest
> chance to work.
Yeah, I'm embarrassed to say we missed that in the commit for that code.
I'll be fixing it up asap.
> Maybe it's time to decouple the 2.6 read/write code
> from the 2.4 code and implement proper vectored operations everywhere?
Probably - we've got limited resources, so patches are welcome :)
> (and kill tge O_DIRECT vs O_APPEN hack, and the broken fallback code,
> and..)
No comment :)
--Mark
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
prev parent reply other threads:[~2004-08-30 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 8:50 [Ocfs2-devel] 2.6 I/O path totally messed up Christoph Hellwig
2004-08-30 11:10 ` Mark Fasheh [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=20040830161052.GC15160@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.