linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kendrick M. Smith" <kmsmith@umich.edu>
To: <bwatson@kahuna.cag.cpqcorp.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.18-pre9, trylock for read/write semaphores
Date: Thu, 21 Feb 2002 13:04:18 -0500 (EST)	[thread overview]
Message-ID: <Pine.SOL.4.33.0202211255240.9973-100000@robotron.gpcc.itd.umich.edu> (raw)


On Tue Feb 12 2002, 17:45:00 EST, Brian Watson wrote:

> Marcelo-
>
> Attached is a patch that adds trylock routines for read/write
> semaphores. David Howells saw it last August and thought it was ready
> to be submitted then, but I became distracted and haven't taken the
> time to submit it until now. My motivation is that Christoph Hellwig
> says he needs it for JFS.

I just returned from vacation and saw this thread.  I also need trylock()
routines for read-write semaphores for NFS version 4, but you're way ahead
of me: I hadn't even started to implement them yet, and have been working
around the deficiency.  So I would really like to see some variant of this
patch go into the 2.5.x series eventually.  Anything I can do to help out?

Cheers,
 Kendrick Smith
 Center for Information Technology and Integration, University of Michigan


             reply	other threads:[~2002-02-21 18:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 18:04 Kendrick M. Smith [this message]
2002-02-21 21:54 ` [PATCH] 2.4.18-pre9, trylock for read/write semaphores Brian J. Watson
2002-02-21 23:02   ` Kendrick M. Smith
2002-02-21 23:26     ` Brian J. Watson
  -- strict thread matches above, loose matches on Subject: below --
2002-02-12 22:45 bwatson
2002-02-12 23:29 ` Alan Cox
2002-02-13  1:47   ` Brian J. Watson
2002-02-13  7:47   ` David Howells
2002-02-13  8:19 ` David Howells
2002-02-14  0:13   ` Brian J. Watson

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=Pine.SOL.4.33.0202211255240.9973-100000@robotron.gpcc.itd.umich.edu \
    --to=kmsmith@umich.edu \
    --cc=bwatson@kahuna.cag.cpqcorp.net \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).