From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Nick Piggin <npiggin@suse.de>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: Re: [PATCH ver3] exofs: New truncate sequence
Date: Tue, 01 Jun 2010 14:52:28 +0300 [thread overview]
Message-ID: <4C04F47C.5020509@panasas.com> (raw)
In-Reply-To: <20100601113620.GA4647@lst.de>
On 06/01/2010 02:36 PM, Christoph Hellwig wrote:
> On Tue, Jun 01, 2010 at 02:31:30PM +0300, Boaz Harrosh wrote:
>> +static int _do_truncate(struct inode *inode, loff_t newsize)
>> {
>> struct exofs_i_info *oi = exofs_i(inode);
>> int ret;
>>
>> inode->i_mtime = inode->i_ctime = CURRENT_TIME;
>>
>> + ret = exofs_oi_truncate(oi, (u64)newsize);
>> + EXOFS_DBGMSG("(0x%lx) size=0x%llx\n", inode->i_ino, newsize);
>> return ret;
>
> Maybe I'm beeing picky, but I really don't see the need for this
> function either, especially given that is has a single caller.
>
It's fine.
It must stay for a very hidden reason. In the pnfs tree, this inside
chunk is preformed from a callback pointer within the pnfs_recall mechanism.
The pnfs export layer has a recall facility that receives a pointer to
a doer. It will block all layouts, recall the layout, preform the doer
let in layouts, and return. So this is split this way to minimize maintenance
efforts.
See an old patch here:
http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=commitdiff;h=ec3c599368550b0cf792738ae6448c932244df51
specifically the small hunk at inode.c
Thanks
Boaz
next prev parent reply other threads:[~2010-06-01 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 12:30 [RFC] exofs: New truncate sequence Boaz Harrosh
2010-05-31 13:44 ` Nick Piggin
2010-05-31 14:13 ` Boaz Harrosh
2010-05-31 14:33 ` Nick Piggin
2010-05-31 14:50 ` Boaz Harrosh
2010-05-31 15:09 ` Nick Piggin
2010-05-31 15:19 ` Boaz Harrosh
2010-06-01 10:08 ` Christoph Hellwig
2010-06-01 10:26 ` Boaz Harrosh
2010-06-01 10:44 ` Christoph Hellwig
2010-06-01 11:05 ` Boaz Harrosh
2010-06-01 11:06 ` Christoph Hellwig
2010-06-01 10:28 ` [PATCH ver2] " Boaz Harrosh
2010-06-01 10:43 ` Christoph Hellwig
2010-06-01 10:59 ` Boaz Harrosh
2010-06-01 11:06 ` Christoph Hellwig
2010-06-01 11:31 ` [PATCH ver3] " Boaz Harrosh
2010-06-01 11:36 ` Christoph Hellwig
2010-06-01 11:52 ` Boaz Harrosh [this message]
2010-06-01 15:09 ` Nick Piggin
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=4C04F47C.5020509@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=osd-dev@open-osd.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 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.