From: Ray Lee <ray-lk@madrabbit.org>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
sct@redhat.com, pbadari@us.ibm.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] ext3 reservation allow turn off for specifed file
Date: Wed, 20 Oct 2004 10:55:41 -0700 [thread overview]
Message-ID: <1098294941.18850.4.camel@orca.madrabbit.org> (raw)
In-Reply-To: <1098147705.8803.1084.camel@w-ming2.beaverton.ibm.com>
On Mon, 2004-10-18 at 18:01 -0700, Mingming Cao wrote:
> On Mon, 2004-10-18 at 16:42, Andrew Morton wrote:
> > Applications currently pass a seeky-access hint into the kernel via
> > posix_fadvise(POSIX_FADV_RANDOM). It would be nice to hook into that
[...]
> Just thought seeky random write application could use the existing ioctl
> to let the kernel know it does not need reservation at all. Isn't that
> more straightforward?
Going the ioctl route seems to imply that userspace would have to do a
posix_fadvise() call and the ioctl, as opposed to just the fadvise. No?
I'm betting the fadvise call is a little more portable as well.
Ray
next prev parent reply other threads:[~2004-10-20 18:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 13:27 Ext3 -mm reservations code: is this fix really correct? Stephen C. Tweedie
2004-10-15 16:01 ` [Ext2-devel] " mingming cao
2004-10-15 16:40 ` Stephen C. Tweedie
2004-10-15 20:29 ` mingming cao
2004-10-15 22:20 ` Stephen C. Tweedie
2004-10-15 22:34 ` mingming cao
2004-10-18 22:55 ` [PATCH 2/3] ext3 reservation allow turn off for specifed file Mingming Cao
2004-10-18 23:42 ` Andrew Morton
2004-10-19 1:01 ` Mingming Cao
2004-10-20 17:55 ` Ray Lee [this message]
2004-10-25 20:33 ` [Ext2-devel] " Mingming Cao
2004-10-25 23:05 ` Mingming Cao
2004-10-25 23:45 ` Andrew Morton
2004-10-26 16:53 ` Mingming Cao
2004-10-26 20:18 ` Andrew Morton
2004-10-26 23:01 ` Mingming Cao
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=1098294941.18850.4.camel@orca.madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox