public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Light-weight dynamically extended stacks
Date: Tue, 20 Dec 2005 17:43:17 +0100	[thread overview]
Message-ID: <20051220164316.GG6789@stusta.de> (raw)
In-Reply-To: <20051220002759.GE3356@waste.org>

On Mon, Dec 19, 2005 at 06:27:59PM -0600, Matt Mackall wrote:
>...
> So why am I raising this idea now at all? Because I think Neil's patch
> is too clever and too specific to block layer stacking and I'd rather
> have a more general solution. Block is by no means the only part of
> the system that allows nesting and pathological combinations surely
> still exist. And will be introduced in the future.
> 
> Also note that my approach might make it reasonable to use one-page
> stacks everywhere, not just on x86.
>...

I'm really looking forward to seeing your patch.

It will e.g. be interesting to measure whether there'll be any 
performance impact.

And since after this patch driver authors might become more sloppy with 
stack usage since there's no longer a hard limit, it will be especially 
interesting to see how you'll implement ensuring that there are no 
additional stack usages > 1 kB between two invocations of you check 
function, because otherwise your patch won't work reliable.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-12-20 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19  0:12 Light-weight dynamically extended stacks Matt Mackall
2005-12-19  8:45 ` Arjan van de Ven
2005-12-19 18:36 ` Adrian Bunk
2005-12-20  0:27   ` Matt Mackall
2005-12-20 16:43     ` Adrian Bunk [this message]
2005-12-20 18:30       ` Matt Mackall
2005-12-20 19:40         ` Patrick McLean
2005-12-21  5:57           ` Valdis.Kletnieks

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=20051220164316.GG6789@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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