mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use mutex instead of semaphore in tty_io.c
Date: Wed, 25 Apr 2007 20:13:59 +0100	[thread overview]
Message-ID: <20070425191359.GA13241@infradead.org> (raw)
In-Reply-To: <20070425154934.GP6798@traven>

On Wed, Apr 25, 2007 at 05:49:34PM +0200, Matthias Kaehlcke wrote:
> drivers/char/tty_io.c uses a semaphore as mutex. use the mutex API
> instead of the (binary) semaphore

This looks like it should be a spinlock:

> -		down(&allocated_ptys_lock);
> +		mutex_lock(&allocated_ptys_lock);
>  		idr_remove(&allocated_ptys, idx);
> -		up(&allocated_ptys_lock);
> +		mutex_unlock(&allocated_ptys_lock);

idr_remove is a quick operation that doesn't sleep.

> @@ -2639,24 +2639,24 @@ static int ptmx_open(struct inode * inode, struct file * filp)
>  	nonseekable_open(inode, filp);
>  
>  	/* find a device that is not in use. */
> -	down(&allocated_ptys_lock);
> +	mutex_lock(&allocated_ptys_lock);
>  	if (!idr_pre_get(&allocated_ptys, GFP_KERNEL)) {
> -		up(&allocated_ptys_lock);

The idr_pre_get should be moved out of the lock, that's the whole
point for it's existance..

> +		mutex_unlock(&allocated_ptys_lock);
>  		return -ENOMEM;
>  	}
>  	idr_ret = idr_get_new(&allocated_ptys, NULL, &index);
>  	if (idr_ret < 0) {
> -		up(&allocated_ptys_lock);
> +		mutex_unlock(&allocated_ptys_lock);
>  		if (idr_ret == -EAGAIN)
>  			return -ENOMEM;
>  		return -EIO;
>  	}
>  	if (index >= pty_limit) {
>  		idr_remove(&allocated_ptys, index);
> -		up(&allocated_ptys_lock);
> +		mutex_unlock(&allocated_ptys_lock);
>  		return -EIO;
>  	}
> -	up(&allocated_ptys_lock);
> +	mutex_unlock(&allocated_ptys_lock);

And idr_get_new is another quick, non-blocking operation.


  reply	other threads:[~2007-04-25 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 15:49 Matthias Kaehlcke
2007-04-25 19:13 ` Christoph Hellwig [this message]
2007-04-25 19:46   ` Matthias Kaehlcke
2007-04-25 19:45     ` Christoph Hellwig
2007-05-31 13:42       ` Matthias Kaehlcke
2007-05-31 13:59         ` Christoph Hellwig
2007-05-31 22:37         ` Andrew Morton
2007-06-01  7:48           ` Matthias Kaehlcke
2007-04-26  2:20   ` Andrew Morton

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=20070425191359.GA13241@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.kaehlcke@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome