From: Andi Kleen <ak@suse.de>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Andi Kleen <ak@suse.de>, Brian Gerst <bgerst@didntduck.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: kmalloc() allocation.
Date: Tue, 31 Oct 2000 10:25:00 +0100 [thread overview]
Message-ID: <20001031102500.A25854@gruyere.muc.suse.de> (raw)
In-Reply-To: <20001031095410.A25158@gruyere.muc.suse.de> <Pine.LNX.4.21.0010310906310.1604-100000@saturn.homenet>
In-Reply-To: <Pine.LNX.4.21.0010310906310.1604-100000@saturn.homenet>; from tigran@veritas.com on Tue, Oct 31, 2000 at 09:07:29AM +0000
On Tue, Oct 31, 2000 at 09:07:29AM +0000, Tigran Aivazian wrote:
> On Tue, 31 Oct 2000, Andi Kleen wrote:
>
> > On Tue, Oct 31, 2000 at 08:49:02AM +0000, Tigran Aivazian wrote:
> > >
> > > what do you mean?! That is, of course, impossible because it would break
> > > all existing software, so I won't even bother checking the code, safely
> > > assuming that you perhaps meant something else, ok?
> >
> > He refers to faulting into the page table from a master table, not faulting
> > from disk.
> >
>
> Ah, ok then. Thanks Andi, I was a bit worried that the world has changed
> too radically for me to catch up :)
Well, unless I'm missing something major the new method is racy (it does
not handle vmalloc-vfree-vmalloc of same area on a different CPU)
-Andi
-
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/
prev parent reply other threads:[~2000-10-31 9:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 15:57 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 13:35 ` Rik van Riel
2000-10-31 13:59 ` Richard B. Johnson
2000-10-31 15:57 ` Pauline Middelink
2000-10-31 15:17 ` Ingo Oeser
2000-10-31 16:11 ` Rik van Riel
2000-10-31 18:22 ` Ingo Oeser
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 [this message]
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=20001031102500.A25854@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=bgerst@didntduck.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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
all inboxes | Powered by JetHome®