From: Andrea Arcangeli <andrea@suse.de>
To: Maneesh Soni <smaneesh@sequent.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.10pre7aa1
Date: Tue, 11 Sep 2001 13:12:38 +0200 [thread overview]
Message-ID: <20010911131238.N715@athlon.random> (raw)
In-Reply-To: <20010911150946.A14621@sequent.com>
In-Reply-To: <20010911150946.A14621@sequent.com>; from smaneesh@sequent.com on Tue, Sep 11, 2001 at 03:09:46PM +0530
On Tue, Sep 11, 2001 at 03:09:46PM +0530, Maneesh Soni wrote:
>
> In article <20010910200344.C714@athlon.random> you wrote:
> > Long term of course, but with my further changes before the inclusion
> > the plain current patches shouldn't apply any longer, I'd like if the
> > developers of the current rcu fd patches could check my changes and
> > adapt them (if they agree with my changes of course ;).
>
> Hello Andrea,
>
> I have noted your changes and I am modifying the FD patch accordingly. In fact
> in the first version of FD patch I have used the rc_callback() interface which
> equivalent to call_rcu().
many thanks. At the moment my biggest concern is about the need of
call_rcu not to be starved by RT threads (keventd can be starved so then
it won't matter if krcud is RT because we won't start using it). But I
don't have concerns about the API so those issues will be transparent to
the FD patch.
Andrea
next prev parent reply other threads:[~2001-09-11 11:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 9:39 2.4.10pre7aa1 Maneesh Soni
2001-09-11 11:12 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-17 9:13 2.4.10pre7aa1 Dipankar Sarma
2001-09-12 11:04 2.4.10pre7aa1 Dipankar Sarma
2001-09-12 14:03 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-12 14:42 ` 2.4.10pre7aa1 Dipankar Sarma
2001-09-12 14:53 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 12:23 ` 2.4.10pre7aa1 Rusty Russell
[not found] <20010910175416.A714@athlon.random>
2001-09-10 17:41 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 18:03 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 18:49 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:01 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 19:03 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:08 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 18:52 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:06 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 17:00 ` 2.4.10pre7aa1 Rik van Riel
2001-09-16 17:23 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 17:34 ` 2.4.10pre7aa1 Rik van Riel
2001-09-16 18:16 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 19:04 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-12 8:24 ` 2.4.10pre7aa1 Rusty Russell
2001-09-11 13:05 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 13:56 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 14:27 ` 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 12:22 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:53 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:57 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 8:51 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:04 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 12:40 ` 2.4.10pre7aa1 Alan Cox
2001-09-11 13:49 ` 2.4.10pre7aa1 Andrea Arcangeli
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=20010911131238.N715@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=smaneesh@sequent.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.