From: David Gibson <david@gibson.dropbear.id.au>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Zhang, Yanmin'" <yanmin_zhang@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftruncate on huge page couldn't extend hugetlb file
Date: Thu, 9 Mar 2006 10:58:05 +1100 [thread overview]
Message-ID: <20060308235805.GC17590@localhost.localdomain> (raw)
In-Reply-To: <200603081828.k28ISgg10244@unix-os.sc.intel.com>
On Wed, Mar 08, 2006 at 10:28:41AM -0800, Chen, Kenneth W wrote:
> Zhang, Yanmin wrote on Tuesday, March 07, 2006 7:25 PM
> > Currently, ftruncate on hugetlb files couldn't extend them. My patch enables it.
> >
> > This patch is against 2.6.16-rc5-mm3 and on the top of the patch which
> > implements mmap on zero-length hugetlb files with PROT_NONE.
>
> > -
> > - inode->i_size = offset;
> > - spin_lock(&mapping->i_mmap_lock);
> > - if (!prio_tree_empty(&mapping->i_mmap))
> > - hugetlb_vmtruncate_list(&mapping->i_mmap, pgoff);
> > - spin_unlock(&mapping->i_mmap_lock);
> > - truncate_hugepages(inode, offset);
> > + if (offset > inode->i_size) {
> > + if (hugetlb_extend_reservation(HUGETLBFS_I(inode), pgoff) != 0)
> > + return -ENOMEM;
> > + inode->i_size = offset;
> > + }
> > + else {
> > +
> > + inode->i_size = offset;
> > + spin_lock(&mapping->i_mmap_lock);
> > + if (!prio_tree_empty(&mapping->i_mmap))
> > + hugetlb_vmtruncate_list(&mapping->i_mmap, pgoff);
> > + spin_unlock(&mapping->i_mmap_lock);
> > + truncate_hugepages(inode, offset);
> > + }
> > return 0;
> > }
>
> Hmm?? I don't think you need to extend the reservation when extending
> hugetlb file via ftruncate. You don't have any vma that pass beyond
> current size. So making a reservation is a wrong thing to do here.
Fwiw, I think truncate *should* extend the reservation. We have a
separate thread arguing about whether we should be reserving by inode
length, as I've implemented, or by which ranges are actually mapped
(as apw's old path implemented). As long as it *is* by inode length -
so it's conceptually all about the logical file in hugetlbfs, not
about any of its mappings - I think it makes sense for an extending
truncate() to extend the reservation. It's not reserving them for any
particular mapping, it's reserving them for page cache pages.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2006-03-09 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 6:21 [PATCH] hugetlb_no_page might break hugetlb quota Zhang, Yanmin
2006-03-06 8:15 ` Chen, Kenneth W
2006-03-06 9:06 ` Zhang, Yanmin
2006-03-08 3:14 ` Zhang, Yanmin
2006-03-08 3:24 ` [PATCH] ftruncate on huge page couldn't extend hugetlb file Zhang, Yanmin
[not found] ` <20060307222148.76e5dc45.akpm@osdl.org>
2006-03-08 6:54 ` Zhang, Yanmin
2006-03-08 18:28 ` Chen, Kenneth W
2006-03-08 23:58 ` David Gibson [this message]
2006-03-09 0:12 ` Chen, Kenneth W
2006-03-09 0:22 ` 'David Gibson'
2006-03-09 0:33 ` Chen, Kenneth W
2006-03-09 1:03 ` 'David Gibson'
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 19:03 Chen, Kenneth W
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=20060308235805.GC17590@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.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