All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shailabh Nagar <nagar@watson.ibm.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-aio@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: libaio 0.3.90 -- test release for sync up
Date: Thu, 05 Sep 2002 15:42:05 -0400	[thread overview]
Message-ID: <3D77B38D.2090402@watson.ibm.com> (raw)
In-Reply-To: 20020905011755.A7979@redhat.com

Ben,

Any updates on when we can see some more "core" aio code for 2.5 ?

Is the code you've been developing substantially the same as in 2.4 ?
 From a brief examination of the 2.4 aio code for raw I/O, it doesn't 
look like it'll need a whole lot of changes except to use bio's. Or do 
you have a different design in place now ?

Any comments/dates will be much appreciated....

- Shailabh

Benjamin LaHaise wrote:
> Hello,
> 
> Well, Andrea seems to be trying to fork libaio, but he never sent 
> any patches to me, so I don't know what his complaint with me as 
> maintainer is.  I hope he finds it in his heart to submit *patches* 
> for any changes he's making.  Anyways, here's a test release going 
> in the direction I've meant to for libaio-0.4.0 -- 0.3.15 is a 
> compatible release for folks running Red Hat Advanced Server and 
> does not break source/binary compatibility.  0.4.0 on the other 
> hand breaks source compatibility to match the changes made for 2.5, 
> but should still provide backwards compatible symbols.  I've also 
> tossed the beginnings of man pages in man/ for people to hack on 
> (Alan, Bert you guys need to synch up with each other on list).  
> ChangeLog bits are below, the test cases have not been updated for 
> the new API, nor has it been tested in any way mean or form.  I'll 
> try to get a 0.3.91 out before I leave tomorrow afternoon, but if 
> not it will wait until Tuesday.
> 
> 		-ben




      reply	other threads:[~2002-09-05 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05  5:17 libaio 0.3.90 -- test release for sync up Benjamin LaHaise
2002-09-05 19:42 ` Shailabh Nagar [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=3D77B38D.2090402@watson.ibm.com \
    --to=nagar@watson.ibm.com \
    --cc=bcrl@redhat.com \
    --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 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.