From: Rusty Russell <rusty@linuxcare.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: prumpf@mandrakesoft.com (Philipp Rumpf), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.1-ac15
Date: Thu, 22 Feb 2001 13:05:04 +1100 [thread overview]
Message-ID: <E14Vl7y-0001FG-00@halfway> (raw)
In-Reply-To: Your message of "Wed, 21 Feb 2001 12:01:26 BST." <E14VXxY-0001wy-00@the-village.bc.nu>
In message <E14VXxY-0001wy-00@the-village.bc.nu> you write:
> > This is a while back, but I thought the solution Philipp and I came up
> > with was to simply used a rw semaphore for this, which was taken (read
> > only) on page fault if we have to scan the exception table.
>
> We can take page faults in interrupt handlers in 2.4 so I had to use a
> spinlock, but that sounds the same
We can? Woah, please explain.
Rusty.
--
Premature optmztion is rt of all evl. --DK
next prev parent reply other threads:[~2001-02-22 2:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 23:15 Linux 2.4.1-ac15 Alan Cox
2001-02-19 9:47 ` Philipp Rumpf
2001-02-19 11:35 ` Alan Cox
2001-02-19 11:54 ` Philipp Rumpf
2001-02-19 16:03 ` Alan Cox
2001-02-19 16:21 ` Philipp Rumpf
2001-02-19 16:27 ` Alan Cox
2001-02-19 16:34 ` Philipp Rumpf
2001-02-19 16:41 ` Alan Cox
2001-02-19 16:48 ` Philipp Rumpf
2001-02-19 17:03 ` Alan Cox
2001-02-21 3:02 ` Rusty Russell
2001-02-21 12:01 ` Alan Cox
2001-02-22 2:05 ` Rusty Russell [this message]
2001-02-22 10:22 ` Alan Cox
2001-02-23 0:01 ` Philipp Rumpf
2001-02-22 2:27 ` Linus Torvalds
2001-02-22 10:29 ` Alan Cox
2001-02-23 20:40 ` Andrea Arcangeli
2001-02-23 21:09 ` Linus Torvalds
2001-02-24 4:04 ` Andrea Arcangeli
2001-02-24 4:54 ` Andrea Arcangeli
2001-02-19 11:54 ` Keith Owens
2001-02-19 12:15 ` Philipp Rumpf
2001-02-19 13:15 ` Keith Owens
2001-02-19 13:25 ` Christoph Hellwig
2001-02-19 21:32 ` Keith Owens
2001-02-19 13:36 ` Philipp Rumpf
2001-02-19 15:23 ` Manfred Spraul
2001-02-19 16:04 ` Alan Cox
2001-02-19 21:52 ` Keith Owens
2001-02-20 12:29 ` Philipp Rumpf
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=E14Vl7y-0001FG-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=prumpf@mandrakesoft.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.