public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony DiSante <theant@nodivisions.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: uninterruptible sleep lockups
Date: Tue, 22 Feb 2005 15:29:51 -0500	[thread overview]
Message-ID: <421B963F.7000204@nodivisions.com> (raw)
In-Reply-To: <421B9309.6080503@nortel.com>

Chris Friesen wrote:
>>> There has been some discussion that these hung
>>> states could be "fixed", but that's absolutely
>>> positively incorrect.
>>
>> That's one of the things I asked a few messages ago.  Some people on 
>> the list were saying that it'd be "really hard" and would "require a 
>> lot of bookkeeping" to "fix" permanently-D-stated processes... which 
>> is completely different than "impossible."
> 
> 
> Nothing is "impossible".

Maybe where you live, but in my world some things are most certainly 
impossible.  Getting a 1MHz CPU to run at 1THz is impossible.  Having the 
kernel automatically install the latest firmware for a buggy device, without 
actually having the new firmware file, is impossible.  Turning your 17" LCD 
monitor into a 50" HDTV is impossible.

> Cracking SHA-256 isn't "impossible", it just 
> takes more computing power than exists on the face of the planet.

Thanks for proving my point.  That's a perfect example of the difference 
between "hard" and "impossible."

> Call it "infeasable" if you like.  It's theoretically possible, but the 
> amount of work and the overhead involved just are not realistic.

Again, that was one of my earlier questions, since some people here were 
saying "impossible" while other were saying "really hard."

-Anthony DiSante
http://nodivisions.com/

  reply	other threads:[~2005-02-22 20:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:18 uninterruptible sleep lockups Anthony DiSante
2005-02-21 19:45 ` Valdis.Kletnieks
2005-02-21 20:24   ` Anthony DiSante
2005-02-21 20:54     ` Valdis.Kletnieks
2005-02-21 22:18       ` Anthony DiSante
2005-02-21 22:43         ` Chris Friesen
2005-02-22  0:06           ` Anthony DiSante
2005-02-22  0:36             ` Valdis.Kletnieks
2005-02-21 22:44       ` Anthony DiSante
2005-02-21 23:11         ` Nish Aravamudan
     [not found]     ` <421B12DB.70603@aitel.hist.no>
2005-02-22 11:16       ` Anthony DiSante
2005-02-22 12:26         ` Denis Vlasenko
2005-02-22 12:35           ` Anthony DiSante
2005-02-22 13:47         ` linux-os
2005-02-22 20:03           ` Anthony DiSante
2005-02-22 20:16             ` Chris Friesen
2005-02-22 20:29               ` Anthony DiSante [this message]
2005-02-22 20:24             ` Horst von Brand
2005-02-22 20:56               ` Chris Friesen
2005-02-22 21:40                 ` linux-os
2005-02-22 23:17                   ` Chris Friesen
2005-02-22 23:42                     ` linux-os
2005-02-23  0:25                       ` Chris Friesen
2005-02-23  1:05                 ` Horst von Brand
2005-02-23 10:04                   ` Bernd Petrovitsch
2005-02-22 21:31 ` Olaf Titz
2005-02-23 16:34   ` Nish Aravamudan
     [not found] <fa.duv6ag6.p5mth0@ifi.uio.no>
     [not found] ` <fa.irk349q.1c3si2o@ifi.uio.no>
2005-02-23  0:59   ` Bodo Eggert
2005-02-23 13:50     ` linux-os
2005-02-24  2:05       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 16:55 Parag Warudkar

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=421B963F.7000204@nodivisions.com \
    --to=theant@nodivisions.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