From: Rusty Russell <rusty@rustcorp.com.au>
To: dipankar@in.ibm.com
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.38-mm2 [PATCH]
Date: Wed, 25 Sep 2002 00:56:17 +1000 [thread overview]
Message-ID: <20020924150424.415792C054@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 24 Sep 2002 15:54:28 +0530." <20020924155428.B4085@in.ibm.com>
In message <20020924155428.B4085@in.ibm.com> you write:
> On Tue, Sep 24, 2002 at 02:41:09PM +1000, Rusty Russell wrote:
> > On Mon, 23 Sep 2002 15:15:59 +0530
> > Dipankar Sarma <dipankar@in.ibm.com> wrote:
> > > Later I will submit a full rcu_ltimer patch that contains
> > > the call_rcu_preempt() interface which can be useful for
> > > module unloading and the likes. This doesn't affect
> > > the non-preemption path.
> >
> > You don't need this: I've dropped the requirement for module
> > unload.
>
> Isn't wait_for_later() similar to synchornize_kernel() or has the
> entire module unloading design been changed since ?
Yes, that was *days* ago 8)
I now just use a synchronize_kernel() which schedules on every CPU,
and disable preempt in magic places.
Ingo growled at me...
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-24 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 4:20 2.5.38-mm2 Andrew Morton
2002-09-23 7:16 ` 2.5.38-mm2 Jens Axboe
2002-09-23 7:43 ` 2.5.38-mm2 Andrew Morton
2002-09-24 21:10 ` 2.5.38-mm2 Bill Davidsen
2002-09-23 9:45 ` 2.5.38-mm2 [PATCH] Dipankar Sarma
2002-09-23 16:28 ` Andrew Morton
2002-09-23 17:33 ` Dipankar Sarma
2002-09-24 4:41 ` Rusty Russell
2002-09-24 10:24 ` Dipankar Sarma
2002-09-24 14:56 ` Rusty Russell [this message]
2002-09-23 9:56 ` 2.5.38-mm2 [PATCH] (dcache) Dipankar Sarma
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=20020924150424.415792C054@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@digeo.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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