public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] vmalloc, kmalloc - 2.4.x
Date: 03 Feb 2003 15:40:29 +0000	[thread overview]
Message-ID: <1044286828.2433.24.camel@gregs> (raw)
In-Reply-To: <1044289102.21009.1.camel@irongate.swansea.linux.org.uk>

On Mon, 2003-02-03 at 16:18, Alan Cox wrote:

> Firstly vmalloc isnt permitted in interrupt context (use kmalloc with GFP_KERNEL),
> although for such small chunks you might want to vmalloc a bigger buffer once
> at startup.
i've allso tried kmalloc with the same result.
Also, in this example it is timer - module isn't cleanly wroted becouse
it supose to be only an example.

-- 
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs


       reply	other threads:[~2003-02-03 15:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1044284924.2402.12.camel@gregs>
     [not found] ` <1044289102.21009.1.camel@irongate.swansea.linux.org.uk>
2003-02-03 15:40   ` Grzegorz Jaskiewicz [this message]
2003-02-03 15:40   ` [BUG] vmalloc, kmalloc - 2.4.x Grzegorz Jaskiewicz
2003-02-03 17:02     ` Benjamin Herrenschmidt
2003-02-03 17:18     ` Alan Cox
2003-02-03 22:54       ` David Woodhouse
2003-02-04  9:35         ` Arjan van de Ven
2003-02-04 12:33         ` Dave Jones
2003-02-03 15:13 Grzegorz Jaskiewicz
2003-02-03 15:19 ` Oliver Neukum
2003-02-03 15:19 ` Arjan van de Ven
2003-02-03 15:35   ` Grzegorz Jaskiewicz
2003-02-03 15:35     ` Arjan van de Ven
2003-02-03 22:52       ` David Woodhouse
2003-02-03 15:22 ` Arjan van de Ven
2003-02-03 15:42   ` Grzegorz Jaskiewicz
2003-02-03 15:52     ` Russell King
2003-02-03 15:58       ` Arnaldo Carvalho de Melo
2003-02-03 16:07       ` Grzegorz Jaskiewicz
2003-02-03 15:39 ` Richard B. Johnson

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=1044286828.2433.24.camel@gregs \
    --to=gj@pointblue.com.pl \
    --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