public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-mips@linux-mips.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS mounting fails on MIPS
Date: Thu, 11 Nov 2010 07:49:52 -0500	[thread overview]
Message-ID: <20101111124952.GA11052@infradead.org> (raw)
In-Reply-To: <AANLkTik=-jiE5xeJCTQZnbf7AFk7Wzap5ToBDceqsEdH@mail.gmail.com>

On Thu, Nov 11, 2010 at 11:10:33AM +0530, Ajeet Yadav wrote:
> I think mips folks agree with the change. I really wish to have there
> comment.
> 
> I also wish to know do we really need fix in XFS for virtual indexed
> architecture, I think its generic issue as many architecture now use VIVT or
> VIPT caches. Do we want to say XFS is relatively unstable with virtual
> indexed architecture ?

The vmap flushing APIs I repeatedly pointed you at are the generic
solution.  They've been implement for arm, parisc and sh already, it's
just that no one has bothered to do it for mips yet.

Without the proper flushing anything that uses vmap, which includes
XFS is not "relatively unstable" but in fact not usable on systems
with virtually indexed caches.

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

  reply	other threads:[~2010-11-11 12:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  5:57 XFS mounting fails on MIPS Ajeet Yadav
2010-11-04 10:23 ` Stan Hoeppner
2010-11-04 12:40 ` Dave Chinner
2010-11-04 12:50 ` Christoph Hellwig
2010-11-09 11:13   ` Ajeet Yadav
2010-11-09 14:05     ` Christoph Hellwig
2010-11-11  4:57       ` Ajeet Yadav
2010-11-11  5:40         ` Ajeet Yadav
2010-11-11 12:49           ` Christoph Hellwig [this message]
2010-11-11 14:56             ` Ajeet Yadav

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=20101111124952.GA11052@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