From: Christoph Hellwig <hch@infradead.org>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: linux-mips@linux-mips.org, xfs@oss.sgi.com
Subject: Re: XFS: bad clientid on recovery on MIPS (VIPT cache)
Date: Mon, 25 Oct 2010 09:43:11 -0400 [thread overview]
Message-ID: <20101025134310.GA3758@infradead.org> (raw)
In-Reply-To: <AANLkTimFuG6cVLkYt+7-Y_8PnapFvmry5RUcmpOHaPco@mail.gmail.com>
On Thu, Oct 21, 2010 at 06:57:15PM +0530, Ajeet Yadav wrote:
> Thanks for response,
>
> Linux kernel I am using is 2.6.30, where as XFS I have ported until 2.6.34
> on given kernel.
> Do you think I need the mentioned API
> flush_kernel_vmap_range/invalidate_kernel_vmap_range in 2.6.30.9 as well.I
> will be grateful if you can provide me sample code for the above API.
I don't really know how to implement it - it's up to the cache
architecture. Take a look at the existing implementations in 2.6.34+
kernels and possibly ask on the Linux-mips mainglinglist how to
implement it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-25 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:11 XFS: bad clientid on recovery on MIPS (VIPT cache) Ajeet Yadav
2010-10-21 12:47 ` Ajeet Yadav
2010-10-21 12:52 ` Christoph Hellwig
2010-10-21 13:27 ` Ajeet Yadav
2010-10-22 5:25 ` Ajeet Yadav
2010-10-25 13:43 ` Christoph Hellwig
2010-11-02 6:35 ` Ajeet Yadav
2010-10-25 13:43 ` Christoph Hellwig [this message]
[not found] <AQHMGZPV5VwDWzpPGkmBdYCEZM2g7JYAfYLwgAAGIHA=>
[not found] ` <BAB94DBB0E89D8409949BC28AC95914C6875A2@USMAExch1.tad.internal.tilera.com>
2012-01-09 7:22 ` Ajeet Yadav
2012-01-09 7:28 ` Ajeet Yadav
2012-01-10 10:30 ` Tony Lu
2012-01-11 11:43 ` Christoph Hellwig
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=20101025134310.GA3758@infradead.org \
--to=hch@infradead.org \
--cc=ajeet.yadav.77@gmail.com \
--cc=linux-mips@linux-mips.org \
--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