| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfstests 013 - 2.6.35.11 - hang |
| From: | Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx> |
| Date: | Mon, 2 May 2011 11:11:14 +0530 |
| Cc: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YHb8XRfnAo/pqbY3dvzaVKb2aRCnwFdetmQmYZ3dd3M=; b=XE06kXUU/LbR3QJyYdNvuzshmAMTZ0Peh+PNPW60ZXxW89lUAO+dbhKb0ilv8AIKMx b4tVGuK/ew01v2PtMgGf94ly4TRHxOEywyZTcjvqpaBUslRXkY6ma44rc9aSf8+xnyJe ZeGTLiC3MtbMvPncdUQ8PawGHlcFR42fsxq9I= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LU9UL52g/Z+DUAhhXJdZfYPN7sqQ7/i+JXTO2UzVI8QUkNgGzZ2OMfqOgEB7BsHYkj mzVOMWHoVvxvp9D3oActJf8BR1+6KV/aX8MZ2mbH2E6X9RZbXt3xp1MXoakDTHJdOhyb x3bla75jgL6+IR2+tbldC9JAnjAW9CQ/2CzEY= |
| In-reply-to: | <BANLkTi=xpSa2x4vaD4zQjrz3_JSLkC-hgg@xxxxxxxxxxxxxx> |
| References: | <BANLkTimAXUtO=oxmLUaHLaRBnGafGP-9kg@xxxxxxxxxxxxxx> <20110427171107.GA29196@xxxxxxxxxxxxx> <BANLkTi=xpSa2x4vaD4zQjrz3_JSLkC-hgg@xxxxxxxxxxxxxx> |
Is there any thing I left out in xfs related to cache coherency.
On Thu, Apr 28, 2011 at 12:59 PM, Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx> wrote:
> MIPS32® 34K™ Core
> It does not provide invalidate_kernel_vmap_range() /
> flush_kernel_vmap_range() to deal with cache coherency problem
> Therefore we provided dma_cache_inv() / dma_cache_wback_inv() , after
> that we did not had any coherency problem
> But as you saying it still has cache coherency problem, wrt xfstests 001 ?
>
> diff -Nurp -X linux-2.6.35.11/Documentation/dontdiff
> linux-2.6.35.11/fs/xfs/linux-2.6/xfs_buf.c
> linux-2.6.35.11-dirty/fs/xfs/linux-2.6/xfs_buf.c
> --- linux-2.6.35.11/fs/xfs/linux-2.6/xfs_buf.c 2011-02-07
> 04:04:07.000000000 +0900
> +++ linux-2.6.35.11-dirty/fs/xfs/linux-2.6/xfs_buf.c 2011-03-22
> 18:29:09.000000000 +0900
> @@ -1192,7 +1192,7 @@ xfs_buf_bio_end_io(
> xfs_buf_ioerror(bp, -error);
>
> if (!error && xfs_buf_is_vmapped(bp) && (bp->b_flags & XBF_READ))
> - invalidate_kernel_vmap_range(bp->b_addr,
> xfs_buf_vmap_len(bp));
> + dma_cache_inv((unsigned long)bp->b_addr,
> xfs_buf_vmap_len(bp));
>
> do {
> struct page *page = bvec->bv_page;
> @@ -1304,7 +1304,7 @@ next_chunk:
> submit_io:
> if (likely(bio->bi_size)) {
> if (xfs_buf_is_vmapped(bp)) {
> - flush_kernel_vmap_range(bp->b_addr,
> + dma_cache_wback_inv((unsigned long)bp->b_addr,
> xfs_buf_vmap_len(bp));
> }
> submit_bio(rw, bio);
>
> On Wed, Apr 27, 2011 at 10:41 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
>> Does 001 also fail for say ext2 and ext3?
>>
>>
>
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch] xfsprogs: fixes a regression hang in xfs_repair phase 4, Ajeet Yadav |
|---|---|
| Next by Date: | Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38, Markus Trippelsdorf |
| Previous by Thread: | Re: [patch] xfsprogs: fixes a regression hang in xfs_repair phase 4, Ajeet Yadav |
| Next by Thread: | Re: xfstests 013 - 2.6.35.11 - hang, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |