From: Christoph Hellwig <hch@lst.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] 2.6 I/O path totally messed up
Date: Mon Aug 30 08:50:25 2004 [thread overview]
Message-ID: <20040830135022.GA17620@lst.de> (raw)
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. Maybe it's time to decouple the 2.6 read/write code
from the 2.4 code and implement proper vectored operations everywhere?
(and kill tge O_DIRECT vs O_APPEN hack, and the broken fallback code,
and..)
next reply other threads:[~2004-08-30 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 8:50 Christoph Hellwig [this message]
2004-08-30 11:10 ` [Ocfs2-devel] 2.6 I/O path totally messed up Mark Fasheh
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=20040830135022.GA17620@lst.de \
--to=hch@lst.de \
--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.