From: Dipankar Sarma <dipankar@in.ibm.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Paul McKenney <paul.mckenney@us.ibm.com>
Subject: Re: [PATCH] New Read-Copy Update patch
Date: Wed, 6 Feb 2002 14:23:03 +0530 [thread overview]
Message-ID: <20020206142303.A1627@in.ibm.com> (raw)
In-Reply-To: <20020205211826.B32506@in.ibm.com> <20020205181354.M3135@athlon.random> <20020206000420.B427@in.ibm.com> <E16YNgv-0002MZ-00@starship.berlin>
In-Reply-To: <E16YNgv-0002MZ-00@starship.berlin>; from phillips@bonn-fries.net on Wed, Feb 06, 2002 at 09:44:33AM +0100
On Wed, Feb 06, 2002 at 09:44:33AM +0100, Daniel Phillips wrote:
> On February 5, 2002 07:34 pm, Dipankar Sarma wrote:
> >
> > + * Based on the original work by Paul McKenney <paul.mckenney@us.ibm.com>
> > + * and inputs from Andrea Arcangeli, Rusty Russell, Andi Kleen etc.
> > + * Papers:
> > + * http://www.rdrop.com/users/paulmck/paper/rclockpdcsproof.pdf
>
> $ wget http://www.rdrop.com/users/paulmck/paper/rclockpdcsproof.pdf
> --09:40:31-- http://www.rdrop.com/users/paulmck/paper/rclockpdcsproof.pdf
> => `rclockpdcsproof.pdf'
> Connecting to www.rdrop.com:80... connected!
> HTTP request sent, awaiting response... 403 Forbidden
> 09:40:32 ERROR 403: Forbidden.
>
> > + * http://lse.sourceforge.net/locking/rclock_OLS.2001.05.01c.sc.pdf (OLS2001)
>
> $ wget http://lse.sourceforge.net/locking/rclock_OLS.2001.05.01c.sc.pdf
> --09:41:59-- http://lse.sourceforge.net/locking/rclock_OLS.2001.05.01c.sc.pdf
> => `rclock_OLS.2001.05.01c.sc.pdf'
> Connecting to lse.sourceforge.net:80... connected!
> HTTP request sent, awaiting response... 404 Not Found
> 09:41:59 ERROR 404: Not Found.
>
> --
> Daniel
Could you try this for the original paper -
http://www.rdrop.com/users/paulmck/rclock/rclockpdcsproof.pdf
Looks like Paul has rearranged his paper site.
And I messed up while rearranging the stuff in LSE. I have now restored
the link to the OLS paper. Could you please retry ?
Sorry about the inconvenience.
Thanks
Dipankar
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-02-06 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 15:48 [PATCH] New Read-Copy Update patch Dipankar Sarma
2002-02-05 16:54 ` Christoph Hellwig
2002-02-05 16:57 ` Ingo Molnar
2002-02-05 18:41 ` Dipankar Sarma
2002-02-05 18:17 ` Dipankar Sarma
2002-02-05 17:13 ` Andrea Arcangeli
2002-02-05 18:34 ` Dipankar Sarma
2002-02-06 8:44 ` Daniel Phillips
2002-02-06 8:53 ` Dipankar Sarma [this message]
2002-02-06 8:58 ` Daniel Phillips
2002-02-06 10:47 ` [PATCH] New Read-Copy Update patch [fixed] 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=20020206142303.A1627@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@us.ibm.com \
--cc=phillips@bonn-fries.net \
--cc=rusty@rustcorp.com.au \
/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