All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauline Middelink <middelink@polyware.nl>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: kmalloc() allocation.
Date: Tue, 31 Oct 2000 16:57:02 +0100	[thread overview]
Message-ID: <20001031165702.A21402@polyware.nl> (raw)
In-Reply-To: <Pine.LNX.4.21.0010311134590.23139-100000@duckman.distro.conectiva> <Pine.LNX.3.95.1001031084051.13415A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1001031084051.13415A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Oct 31, 2000 at 08:59:53AM -0500

On Tue, 31 Oct 2000 around 08:59:53 -0500, Richard B. Johnson wrote:
[snip]

> Since Linux is starting to be used in many 'strange' non-desktop
> environments, maybe it's time to provide a hook to reserve the
> top N kilobytes of RAM for strange buffers. Like:
> 
> 	append="..,reserve=2M".
> 
> Upon startup, a pointer, valid when using the kernel DS, could be
> initialized to point to the beginning of this area. This is essentially
> zero overhead for the kernel because it just points to one longword
> greater than the RAM the kernel will use.

Please look at bigphysarea, it allocates a piece of meory at boottime
and has a small allocator over it to dispatch it to drivers. Mostly
video framegrabbers at this time... But the interface et all is there...

	http://www.polyware.nl/~middelink/En/hob-v4l.html

    Met vriendelijke groet,
        Pauline Middelink
-- 
PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0  58 A3 06 9D B6 34 39 E2
For more details look at my website http://www.polyware.nl/~middelink
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-31 15:57 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 15:57 kmalloc() allocation Richard B. Johnson
2000-10-30 16:06 ` Tigran Aivazian
2000-10-30 16:28   ` Richard B. Johnson
2000-10-30 16:38     ` Tigran Aivazian
2000-10-30 17:57       ` Richard B. Johnson
2000-10-30 16:06 ` John Levon
2000-10-30 16:27   ` Richard B. Johnson
2000-10-30 16:49     ` Jeff Garzik
2000-10-30 16:54       ` Tigran Aivazian
2000-10-30 17:08         ` Jeff Garzik
2000-10-30 18:08           ` Richard B. Johnson
2000-10-30 18:06       ` Richard B. Johnson
2000-10-30 18:10         ` Jeff Garzik
2000-10-30 16:40 ` Rik van Riel
2000-10-31  7:03   ` Mike Galbraith
2000-10-31 10:48   ` Ingo Oeser
2000-10-31 10:48     ` Ingo Oeser
2000-10-31 13:35     ` Rik van Riel
2000-10-31 13:35       ` Rik van Riel
2000-10-31 13:59       ` Richard B. Johnson
2000-10-31 13:59         ` Richard B. Johnson
2000-10-31 15:57         ` Pauline Middelink [this message]
2000-10-31 15:17       ` Ingo Oeser
2000-10-31 15:17         ` Ingo Oeser
2000-10-31 16:11         ` Rik van Riel
2000-10-31 16:11           ` Rik van Riel
2000-10-31 18:22           ` Ingo Oeser
2000-10-31 18:22             ` Ingo Oeser
2000-10-31 14:43     ` afei
2000-10-31 14:43       ` afei
2000-10-30 18:22 ` Alan Cox
2000-10-30 18:37   ` Richard B. Johnson
2000-10-31  5:28     ` H. Peter Anvin
2000-10-31  6:11       ` Brian Gerst
2000-10-31  8:44         ` Andi Kleen
2000-10-31 12:58           ` Brian Gerst
2000-10-31 14:48             ` kernel
2000-10-31 15:01               ` Alan Cox
2000-10-31 15:57                 ` kernel
2000-10-31  8:49         ` Tigran Aivazian
2000-10-31  8:54           ` Andi Kleen
2000-10-31  9:07             ` Tigran Aivazian
2000-10-31  9:25               ` 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=20001031165702.A21402@polyware.nl \
    --to=middelink@polyware.nl \
    --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 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.