All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Prakash Sangappa <prakash.sangappa@oracle.com>,
	linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, peterz@infradead.org,
	dave@stgolabs.net, manfred@colorfullife.com,
	Prakash Sangappa <prakash.sangappa@oracle.com>
Subject: Re: [PATCH v2] ipc: Update semtimedop() to use hrtimer
Date: Thu, 28 Apr 2022 21:26:55 +0200	[thread overview]
Message-ID: <874k2dovpc.ffs@tglx> (raw)
In-Reply-To: <1651158422-28014-1-git-send-email-prakash.sangappa@oracle.com>

Prakash,

On Thu, Apr 28 2022 at 08:07, Prakash Sangappa wrote:
> semtimedop() should be converted to use hrtimer like it has been done
> for most of the system calls with timeouts. This system call already
> takes a struct timespec as an argument and can therefore provide finer
> granularity timed wait.

almost perfect :)

The v1->v2: description wants to be below the '---' separator. It's not
part of the changelog and just helpful for reviewers to assess the
history of the patch(set).

> v1->v2:
>   - Use timespec64_valid() to validate timeout
>      and other changes as suggested by Thomas Gleixner
>
> Signed-off-by: Prakash Sangappa <prakash.sangappa@oracle.com>
> ---
...
> @@ -2210,7 +2209,7 @@ long __do_semtimedop(int semid, struct sembuf *sops,
>  		/*
>  		 * If an interrupt occurred we have to clean up the queue.
>  		 */
> -		if (timeout && jiffies_left == 0)
> +		if (timed_out)
>  			error = -EAGAIN;
>  	} while (error == -EINTR && !signal_pending(current)); /* spurious */

Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

      reply	other threads:[~2022-04-28 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 15:07 [PATCH v2] ipc: Update semtimedop() to use hrtimer Prakash Sangappa
2022-04-28 19:26 ` Thomas Gleixner [this message]

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=874k2dovpc.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=peterz@infradead.org \
    --cc=prakash.sangappa@oracle.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.