linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: DIO panic on 2.6.21.5
Date: Fri, 29 Jun 2007 17:03:46 -0700	[thread overview]
Message-ID: <46859DE2.9040604@us.ibm.com> (raw)
In-Reply-To: 5A6608DF-EDC3-43C1-BFB7-58ACBF94DBCB@oracle.com



Zach Brown wrote:

>
> On Jun 27, 2007, at 8:01 PM, Badari Pulavarty wrote:
>
>> Hi Zach,
>>
>> One of our perf. team ran into this while doing some runs.
>> I didn't see anything obvious - it looks like we converted
>> async IO to synchronous one. I didn't spend much time digging
>> around.
>
>
> It looks pretty bad, a *shouldn't happen* kind of case.  I'm sure it  
> just means I missed some case :/.
>
>> Is this a known issue ? Any ideas ?
>
>
> I haven't seen it before, no.  Do they have a reliable recipe to  
> reproduce it?
>
> In any case, I'll dig in early next week when I'm back from OLS.  I'm  
> pretty confident that we'll be able to find the case.  Please let me  
> know if it's urgent and I should try and find time before then.
>
> Thanks for reporting it.

I asked our perf. team to reproduce and print out refcount, if this 
happens again.
We can look at it when we get back.

Thanks,
Badari



  reply	other threads:[~2007-06-30  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28  3:01 DIO panic on 2.6.21.5 Badari Pulavarty
2007-06-29 22:10 ` Zach Brown
2007-06-30  0:03   ` Badari Pulavarty [this message]
2007-07-03 22:28     ` [PATCH] dio: remove bogus refcounting BUG_ON Zach Brown
2007-07-05  2:25       ` Badari Pulavarty
2007-07-05  3:53         ` Suparna Bhattacharya
2007-07-05 17:11         ` Zach Brown
2007-07-05 17:16           ` Badari Pulavarty
2007-07-05 17:21             ` Zach Brown

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=46859DE2.9040604@us.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zach.brown@oracle.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;
as well as URLs for NNTP newsgroup(s).