All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Tinsley <btinsley@emageon.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20, .text.lock.swap cpu usage? (ibm x440)
Date: Thu, 09 Jan 2003 21:42:06 -0600	[thread overview]
Message-ID: <3E1E410E.5050905@emageon.com> (raw)
In-Reply-To: 20030110032937.GI23814@holomorphy.com

William Lee Irwin III wrote:

>At some point in the past, I wrote:
>  
>
>>>There is no extant implementation of paged stacks yet.
>>>      
>>>
>
>On Thu, Jan 09, 2003 at 09:17:56PM -0600, Brian Tinsley wrote:
>  
>
>>For the most part, this is probably a boundary condition, right? Anyone 
>>that intentionally has 800+ threads in a single application probably 
>>needs to reevaluate their design :)
>>    
>>
>
>IMHO multiprogramming is as valid a use for memory as any other. Or
>even otherwise, it's not something I care to get in design debates
>about, it's just how the things are used.
>
I agree with the philosophy in general, but if I sit down to write a 
threaded application for Linux on IA-32 and wind up with a design that 
uses 800+ threads in any instance (other than a bug, which was our 
case), it's time to give up the day job and start riding on the back of 
the garbage truck ;)

>The only trouble is support for what you're doing is unimplemented.
>
You mean the 800+ threads or Java on Linux?

>At some point in the past, I wrote:
>  
>
>>>I'm working on a different problem (mem_map on 64GB on 2.5.x). I
>>>probably won't have time to implement it in the near future, I
>>>probably won't be doing it vs. 2.4.x, and I won't have to if someone
>>>else does it first.
>>>      
>>>
>
>On Thu, Jan 09, 2003 at 09:17:56PM -0600, Brian Tinsley wrote:
>  
>
>>Is that a hint to someone in particular?
>>    
>>
>
>Only you, if anyone. My intentions and patchwriting efforts on the 64GB
>and highmem multiprogramming fronts are long since public, and publicly
>stated to be targeted at 2.7. Since there isn't a 2.7 yet, 2.5-CURRENT
>must suffice until there is.
>
In all honesty, I would enjoy nothing more than contributing to kernel 
development. Unfortunately it's a bit out of my scope right now (but not 
forever). If I only believed aliens seeded our gene pool with clones, I 
could hook up with those folks that claim to have cloned a human and get 
one of me made! ;)



  reply	other threads:[~2003-01-10  3:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10  3:17 2.4.20, .text.lock.swap cpu usage? (ibm x440) Brian Tinsley
2003-01-10  3:29 ` William Lee Irwin III
2003-01-10  3:42   ` Brian Tinsley [this message]
2003-01-10  3:54     ` William Lee Irwin III
2003-01-10  4:08       ` Brian Tinsley
2003-01-10  4:19         ` William Lee Irwin III
2003-01-10  4:50           ` Brian Tinsley
2003-01-10  5:17             ` Martin J. Bligh
2003-01-10  5:24             ` William Lee Irwin III
2003-01-10  5:45               ` Brian Tinsley
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 23:35 Chris Wood
2003-01-06 23:50 ` William Lee Irwin III
2003-01-06 23:52 ` Andrew Morton
2003-01-09 17:17   ` Chris Wood
2003-01-09 20:18     ` Andrew Morton
2003-01-10  0:25       ` William Lee Irwin III
2003-01-10  0:44         ` Brian Tinsley
2003-01-10  0:55           ` William Lee Irwin III
2003-01-10 20:42       ` Chris Wood
2003-01-09  2:20 ` James Cleverdon
2003-01-09  2:57 ` William Lee Irwin III

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=3E1E410E.5050905@emageon.com \
    --to=btinsley@emageon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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.