[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140925050103.GB20431@gmail.com>
Date: Thu, 25 Sep 2014 07:01:03 +0200
From: Ingo Molnar <mingo@...nel.org>
To: NeilBrown <neilb@...e.de>
Cc: Trond Myklebust <trond.myklebust@...marydata.com>,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Ingo Molnar <mingo@...hat.com>,
linux-fsdevel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Jeff Layton <jeff.layton@...marydata.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 1/5 - resend] SCHED: add some "wait..on_bit...timeout()"
interfaces.
* NeilBrown <neilb@...e.de> wrote:
>
> In commit c1221321b7c25b53204447cff9949a6d5a7ddddc
> sched: Allow wait_on_bit_action() functions to support a timeout
>
> I suggested that a "wait_on_bit_timeout()" interface would not meet my
> need. This isn't true - I was just over-engineering.
>
> Including a 'private' field in wait_bit_key instead of a focused
> "timeout" field was just premature generalization. If some other
> use is ever found, it can be generalized or added later.
>
> So this patch renames "private" to "timeout" with a meaning "stop
> waiting when "jiffies" reaches or passes "timeout",
> and adds two of the many possible wait..bit..timeout() interfaces:
>
> wait_on_page_bit_killable_timeout(), which is the one I want to use,
> and out_of_line_wait_on_bit_timeout() which is a reasonably general
> example. Others can be added as needed.
>
> Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> Signed-off-by: NeilBrown <neilb@...e.de>
>
> ---
> This time with EXPORT_SYMBOL_GPL.
Looks good to me, thanks!
Acked-by: Ingo Molnar <mingo@...nel.org>
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists