All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Chris Mason <clm@fb.com>, Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: don't zero partial page cache pages during O_DIRECT
Date: Fri, 08 Aug 2014 22:19:10 -0500	[thread overview]
Message-ID: <53E5932E.6@redhat.com> (raw)
In-Reply-To: <53E5885A.9090302@fb.com>

On 8/8/14, 9:32 PM, Chris Mason wrote:

>> Go on, call me a deranged monkey on some serious mind-controlling
>> substances. I don't care. :)

Insider / obscure quote achievement unlocked!
 
> The deranged part is invalidating pos -> -1 on a huge file because of a
> single 512b direct read.  But, if you mix O_DIRECT and buffered you get
> what the monkeys give you and like it.

Agreed, I really scratch my head at that one...

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-08-09  3:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 14:35 [PATCH] xfs: don't zero partial page cache pages during O_DIRECT Chris Mason
2014-08-08 15:17 ` Chris Mason
2014-08-08 16:04 ` [PATCH RFC] xfs: use invalidate_inode_pages2_range for DIO writes Chris Mason
2014-08-09  0:48   ` Dave Chinner
2014-08-09  2:42     ` Chris Mason
2014-08-08 20:39 ` [PATCH] xfs: don't zero partial page cache pages during O_DIRECT Brian Foster
2014-08-09  0:36 ` Dave Chinner
2014-08-09  2:32   ` Chris Mason
2014-08-09  3:19     ` Eric Sandeen [this message]
2014-08-09  4:17     ` Dave Chinner
2014-08-09 12:57 ` [PATCH v2] " Chris Mason
2014-08-11 13:29   ` Brian Foster
2014-08-12  1:17   ` Dave Chinner
2014-08-19 19:24     ` Chris Mason
2014-08-19 22:35       ` Dave Chinner
2014-08-20  1:54         ` Chris Mason
2014-08-20  2:19           ` Dave Chinner
2014-08-20  2:36             ` Dave Chinner
2014-08-20  4:41               ` Dave Chinner

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=53E5932E.6@redhat.com \
    --to=sandeen@redhat.com \
    --cc=clm@fb.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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.