[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519075155.GA29242@gondor.apana.org.au>
Date: Tue, 19 May 2015 15:51:55 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Stephan Mueller <smueller@...onox.de>
Cc: Theodore Ts'o <tytso@....edu>, pebolle@...cali.nl,
andreas.steffen@...ongswan.org, sandyinchina@...il.com,
linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org
Subject: Re: [PATCH v6 1/5] random: Blocking API for accessing
nonblocking_pool
On Tue, May 19, 2015 at 09:35:15AM +0200, Stephan Mueller wrote:
>
> Thank you for the hints. I will follow your guidance.
>
> Just for my edification: why is this (rather complex sounding) approach
> preferred over a simple cancel API? Other async APIs (e.g. the AIO syscalls
> with io_cancel) have such cancel operations.
>
> Such cancel function would be as simple as:
You're right. The cancel function is indeed simpler. I can
certainly live with that.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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