From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] odirect hack
Date: Fri, 01 Oct 2010 15:09:45 -0700 [thread overview]
Message-ID: <4CA65C29.7030001@oracle.com> (raw)
Mark,
I was discussing with Joel whether it was time for us to special
case the odirect hack we've had since day 1. The one that allows
concurrent odirect writes.
I am wondering whether we should allow users control that behavior
via a mount option. parallel_directio, maybe.
Sunil
next reply other threads:[~2010-10-01 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 22:09 Sunil Mushran [this message]
2010-10-07 22:38 ` [Ocfs2-devel] odirect hack 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=4CA65C29.7030001@oracle.com \
--to=sunil.mushran@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.