linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Joel Becker <jlbec@evilplan.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm for fs: add truncate_pagecache_range
Date: Sun, 13 May 2012 14:03:03 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.00.1205131354380.1547@eggly.anvils> (raw)
In-Reply-To: <alpine.LSU.2.00.1203231343380.1940@eggly.anvils>

On Fri, 23 Mar 2012, Hugh Dickins wrote:
> I do have patches for ext4, ocfs2 and xfs to use this, but they're too
> late now for v3.4.  However, it would be helpful if this function could
> go ahead into v3.4, so filesystems can convert to it at leisure afterwards.

I just sent out the little ext4 and xfs patches, but decided not
to bother you with the ocfs2 one.  ocfs2 is already doing it right with
unmap_mapping_range; and since file.c is using unmap_mapping_range with
truncate_inode_pages in other places, it seemed wrong to force a different
convention upon you in this one place (perhaps they can all be converted
to truncate_pagecache_range, but if it ain't broke...)

Hugh

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2012-05-13 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 20:46 Hugh Dickins
2012-03-23 21:01 ` Andrew Morton
2012-03-23 21:14   ` Hugh Dickins
2012-03-23 22:59     ` Andrew Morton
2012-03-25 20:26       ` Hugh Dickins
2012-03-25 20:50         ` Andrew Morton
2012-03-25 21:55           ` Hugh Dickins
2012-04-03  5:45         ` Joel Becker
2012-05-13 21:03 ` Hugh Dickins [this message]
2012-05-17  9:25   ` Joel Becker

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=alpine.LSU.2.00.1205131354380.1547@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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