All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: aio stress panic on 2.6.11-mm1
Date: Wed, 9 Mar 2005 16:34:04 +0530	[thread overview]
Message-ID: <20050309110404.GA4088@in.ibm.com> (raw)
In-Reply-To: <18744.1110364438@redhat.com>


Any sense of how costly it is to use spin_lock_irq's vs spin_lock
(across different architectures) ? Isn't rwsem used very widely ?

Regards
Suparna

On Wed, Mar 09, 2005 at 10:33:58AM +0000, David Howells wrote:
> Andrew Morton <akpm@osdl.org> wrote:
> 
> > If we want to take the spinlock from interrupt context, the non-interrupt
> > context code needs to do spin_lock_irq(), not spin_lock().
> 
> Yeah. I think I had a patch for that somewhere, but I think Linus turned it
> down. I can't find any emails on that subject though. I'll knock together a
> new patch for it.
> 
> David
> --
> To unsubscribe, send a message with 'unsubscribe linux-aio' in
> the body to majordomo@kvack.org.  For more info on Linux AIO,
> see: http://www.kvack.org/aio/
> Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

-- 
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India


       reply	other threads:[~2005-03-09 10:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050308170107.231a145c.akpm@osdl.org>
     [not found] ` <1110327267.24286.139.camel@dyn318077bld.beaverton.ibm.com>
     [not found]   ` <18744.1110364438@redhat.com>
2005-03-09 11:04     ` Suparna Bhattacharya [this message]
2005-03-09 11:05       ` aio stress panic on 2.6.11-mm1 Andrew Morton
2005-03-09 11:07       ` Arjan van de Ven
2005-03-09 11:17         ` Andi Kleen
2005-03-09 11:28         ` Andrew Morton
2005-03-09 11:59           ` David Howells
2005-03-09 12:12           ` [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks David Howells
2005-03-09 17:35             ` Badari Pulavarty
2005-03-09 19:18               ` Badari Pulavarty
2005-03-09 19:16             ` Badari Pulavarty
2005-03-09 19:42               ` Andrew Morton
2005-03-09 20:10                 ` Arjan van de Ven
2005-03-11  9:40                   ` Ingo Molnar
2005-03-11 10:07                     ` Andrew Morton
2005-03-11 10:25                       ` Ingo Molnar
2005-03-09 11:10       ` aio stress panic on 2.6.11-mm1 Arjan van de Ven
2005-03-09 11:21         ` Andi Kleen
2005-03-09 14:48           ` Suparna Bhattacharya
2005-03-09 21:58         ` David Howells
2005-03-09 11:11       ` Andi Kleen

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=20050309110404.GA4088@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.