public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: James Dingwall <james.dingwall@zynstra.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ben Myers <bpm@sgi.com>, xfs@oss.sgi.com
Subject: Re: Cleancache support in XFS
Date: Tue, 23 Jul 2013 08:23:00 +0100	[thread overview]
Message-ID: <51EE2F54.80701@zynstra.com> (raw)
In-Reply-To: <20130722154812.GC30300@phenom.dumpdata.com>

Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 19, 2013 at 08:18:12AM +0100, James Dingwall wrote:
>> Konrad Rzeszutek Wilk wrote:
>>> On Fri, May 24, 2013 at 08:30:16AM +0100, James Dingwall wrote:
>>>> Konrad Rzeszutek Wilk wrote:
>>>>> On Thu, May 02, 2013 at 09:24:51AM +0100, James Dingwall wrote:
>>>>>> Dave Chinner wrote:
>>>>>>> On Wed, May 01, 2013 at 11:20:44AM -0500, Ben Myers wrote:
>>>>>>>> Hi James,
>>>>> Hey folks,
>>>>> I am walking through my vacation-emails-mbox.
>>>>>
>>>>>>>> On Wed, May 01, 2013 at 01:39:09PM +0100, James Dingwall wrote:
>>>>>>>>> In reference to: http://oss.sgi.com/archives/xfs/2012-05/msg00046.html
>>>>>>>>>
>>>>>>>>> $ grep -r cleancache fs/xfs
>>>>>>>>> on the 3.9 kernel source suggests that no patch was submitted to
>>>>>>>>> enable cleancache for the XFS filesystem.  Since it was suggested
>>>>>>>>> that this could be a one liner I've had a go and my first effort is
>>>>>>>>> inline below.  While this seems to compile OK I have no experience
>>>>>>>>> in filesystems so I would appreciate it if anyone can point out that
>>>>>>>>> it is obviously wrong and likely to eat my data before I try booting
>>>>>>>>> the kernel.
>>>>>>>>>
>>>>>>>>> If it seems a reasonable attempt what would be the best way to check
>>>>>>>>> that it isn't doing nasty things?
>>>>>>>> Hrm.. Looks like there is a doc in Documentation/vm/cleancache.txt which
>>>>>>>> includes a list of attributes the filesystem needs to have to work properly
>>>>>>>> with cleancache.
>>>>>>> So, those points are:
>>>>>> I had started to look at these too but I feel very out of my depth!
>>>>>> I had similar conclusions to what Dave wrote but I don't think my
>>>>>> thoughts should carry very much (any) weight.  Anyway I gambled and
>>>>>> booted my xen domU with this patch and so far so good...  xen top
>>>>>> shows that tmem is now being used where previously it wasn't.  I'll
>>>>>> try running the xfstests at the weekend after a couple more days up
>>>>>> time to see what happens.
>>>>> And how did it go?
>>>> I am running the patch I created on 3.9.3 on half of my xen guests
>>>> now and have not noticed any stability or filesystem problems.  xl
>>>> top with 'T' shows that the guests running with it are using
>>>> ephemeral pages were those without do not.  I did do some runs with
>>>> xfstests which had some failures but they were present with and
>>>> without the patch.  The best I can really offer is that it works for
>>>> me, ymmv.  The patch is available as commit
>>>> c725011c4fc5d47e12d131f61bd91a58a40036b5 in
>>>> https://github.com/JKDingwall/linux.git xfs-enable-cleancache or in
>>>> the first message of this thread.
>>> Hey James,
>>>
>>> I've run this patch on my local tree and it looks to work right. I am
>>> saying "looks" as I am hitting some other issue that I believe are
>>> unralted to the patch - but I need to figure them out before I can
>>> comfortably say: "Yes, this looks right and works for me as well."
>>>
>>> Stay tuned.
>> Just to add that I have also had no observable problems running this
>> patch on 3.10.0 or 3.10.1.
> Yup. And I tested it as well. In other words if you would like to add
> Acked-by from me that would be super. Thanks!
My patch is now available in https://github.com/JKDingwall/linux.git 
xfs-enable-cleancache as commit id 
6d50663e4ec88b7e1fd872b12ac310b1f4bb38c6.  I have rebased it on 3.10 
with KRW's Acked-by and my Signed-off-by in the commit message.  Is it 
reasonable for this to be considered for 3.12 or would further testing 
be required?

Thanks,
James

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

  reply	other threads:[~2013-07-23  7:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 12:39 Cleancache support in XFS James Dingwall
2013-05-01 16:20 ` Ben Myers
2013-05-01 22:30   ` Dave Chinner
2013-05-02  8:24     ` James Dingwall
2013-05-22 19:28       ` Konrad Rzeszutek Wilk
2013-05-24  7:30         ` James Dingwall
2013-06-07 17:08           ` Konrad Rzeszutek Wilk
2013-07-19  7:18             ` James Dingwall
2013-07-22 15:48               ` Konrad Rzeszutek Wilk
2013-07-23  7:23                 ` James Dingwall [this message]
2013-07-23  8:27                   ` Dave Chinner
2013-07-23  8:53                     ` James Dingwall
2013-11-21 13:35                     ` James Dingwall
2013-11-21 16:07                       ` Ben Myers
2013-11-21 22:12                         ` Dave Chinner
2013-11-26 16:35                           ` Konrad Rzeszutek Wilk
2013-11-26 16:35                         ` Konrad Rzeszutek Wilk
2013-05-13  8:59 ` James Dingwall
  -- strict thread matches above, loose matches on Subject: below --
2012-04-30 17:31 Alexey Vlasov
2012-04-30 19:12 ` Christoph Hellwig
2012-05-02  8:02   ` Alexey Vlasov
2012-05-05 23:40     ` 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=51EE2F54.80701@zynstra.com \
    --to=james.dingwall@zynstra.com \
    --cc=bpm@sgi.com \
    --cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox