public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: "linux-aio kvack.org" <linux-aio@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] Add kernel AIO support for POSIX AIO
Date: Fri, 29 Jul 2005 08:54:25 +0200	[thread overview]
Message-ID: <1122620065.2019.90.camel@frecb000686> (raw)
In-Reply-To: <1122565588.2019.79.camel@frecb000686>

On Thu, 2005-07-28 at 17:46 +0200, Sébastien Dugué wrote:
> infrastructure to be used by user level libraries aiming at implementing
> a POSIX compliant API on top of this kernel support.
> 
>   This patchset is comprised of 5 patches, each implementing a specific
> functionality:
> 
> 	- aiomaxevents: adds a sysctl variable for setting the default 
> 	  AIO context event ring size at runtime. This tunable is 
> 	  accessible via /proc/sys/fs/posix-aio-default-max-nr.
> 
> 	- aioevent: adds support for request completion notification.
> 
> 	- lioevent: adds support for list of requests completion 
> 	  notification.
> 
> 	- liowait: adds support for the POSIX listio LIO_WAIT mechanism.
> 
> 	- cancelfd: adds support for cancellation against a file 
> 	  descriptor.
> 
>  These patches apply cleanly on a vanilla 2.6.12 kernel tree and should 
> be applied in the order shown before.
> 


  Sorry forgot to credit Laurent Vivier as the main author of these
patches.

  Sébastien.

-- 
------------------------------------------------------

  Sébastien Dugué                BULL/FREC:B1-247
  phone: (+33) 476 29 77 70      Bullcom: 229-7770

  mailto:sebastien.dugue@bull.net

  Linux POSIX AIO: http://www.bullopensource.org/posix
  
------------------------------------------------------


      reply	other threads:[~2005-07-29  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 15:46 [PATCH 0/5] Add kernel AIO support for POSIX AIO Sébastien Dugué
2005-07-29  6:54 ` Sébastien Dugué [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=1122620065.2019.90.camel@frecb000686 \
    --to=sebastien.dugue@bull.net \
    --cc=linux-aio@kvack.org \
    --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