public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add execute_in_process_context() API
Date: Wed, 8 Feb 2006 17:07:11 +0100	[thread overview]
Message-ID: <200602081707.11791.ak@suse.de> (raw)
In-Reply-To: <1139414279.3003.25.camel@mulgrave.il.steeleye.com>

On Wednesday 08 February 2006 16:57, James Bottomley wrote:
> On Wed, 2006-02-08 at 16:18 +0100, Andi Kleen wrote:
> > On Wednesday 08 February 2006 16:15, James Bottomley wrote:
> > >  The problem is that
> > > there's no real way to cope with failure in this case.
> > 
> > Then you can't use GFP_ATOMIC. You have to redesign.
> 
> My mailer seems to have deleted the part of the email with your redesign
> suggestion in it...
> 
> My initial point is that the current scsi_reap_target() infrastructure
> is more broken than the new API, so it does represent an improvement. 

An improvement that will randomly fail under high load.

-Andi

  reply	other threads:[~2006-02-08 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1139342419.6065.8.camel@mulgrave.il.steeleye.com.suse.lists.linux.kernel>
2006-02-08  8:06 ` [PATCH] add execute_in_process_context() API Andi Kleen
2006-02-08  8:18   ` Andrew Morton
2006-02-08  8:50     ` Andi Kleen
2006-02-08 15:15   ` James Bottomley
2006-02-08 15:18     ` Andi Kleen
2006-02-08 15:57       ` James Bottomley
2006-02-08 16:07         ` Andi Kleen [this message]
2006-02-08 15:30     ` Tejun
2006-02-08 15:36       ` James Bottomley
2006-02-07 20:00 James Bottomley
2006-02-07 20:26 ` Dave Jones
2006-02-07 20:34   ` Andrew Morton
2006-02-08 12:51 ` Stefan Richter

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=200602081707.11791.ak@suse.de \
    --to=ak@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    /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