From: wcheng@sourceware.org <wcheng@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs ops_file.c
Date: 17 Jan 2007 22:30:14 -0000 [thread overview]
Message-ID: <20070117223014.11168.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: STABLE
Changes by: wcheng at sourceware.org 2007-01-17 22:30:13
Modified files:
gfs-kernel/src/gfs: ops_file.c
Log message:
Remove aio code that was mistakenly added into stable cvs branch.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_file.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.16.6.2.2.6&r2=1.16.6.2.2.7
--- cluster/gfs-kernel/src/gfs/ops_file.c 2006/11/17 20:39:24 1.16.6.2.2.6
+++ cluster/gfs-kernel/src/gfs/ops_file.c 2007/01/17 22:30:12 1.16.6.2.2.7
@@ -646,12 +646,6 @@
if (alloc_required) {
set_bit(GFF_DID_DIRECT_ALLOC, &fp->f_flags);
- /* for asynchronous IO, the buffer can not be splitted */
- if (iocb) {
- count = do_write_direct_alloc(file, buf, size, offset, iocb);
- goto out_iocb_write;
- }
-
/* split large writes into smaller atomic transactions */
while (size) {
s = gfs_tune_get(sdp, gt_max_atomic_write);
@@ -681,7 +675,6 @@
gfs_glock_dq_uninit(&t_gh);
}
- out_iocb_write:
error = 0;
out_gunlock:
next reply other threads:[~2007-01-17 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 22:30 wcheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-30 9:05 [Cluster-devel] cluster/gfs-kernel/src/gfs ops_file.c fabbione
2008-01-28 6:36 fabbione
2007-06-17 3:35 wcheng
2007-06-17 2:56 wcheng
2007-05-24 22:34 wcheng
2007-05-04 14:49 wcheng
2006-11-17 20:39 wcheng
2006-11-17 20:33 wcheng
2006-11-17 20:26 wcheng
2006-11-17 19:49 wcheng
2006-11-17 16:15 wcheng
2006-11-17 5:00 wcheng
2006-10-27 16:22 wcheng
2006-10-24 3:35 wcheng
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=20070117223014.11168.qmail@sourceware.org \
--to=wcheng@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).