From: Benjamin LaHaise <bcrl@redhat.com>
To: Steven Whitehouse <steve@gw.chygwyn.com>
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: [patch] add iocb to network protocols
Date: Fri, 11 Oct 2002 06:27:09 -0400 [thread overview]
Message-ID: <20021011062709.A14784@redhat.com> (raw)
In-Reply-To: <200210110931.KAA19428@gw.chygwyn.com>; from steve@gw.chygwyn.com on Fri, Oct 11, 2002 at 10:31:23AM +0100
On Fri, Oct 11, 2002 at 10:31:23AM +0100, Steven Whitehouse wrote:
> Given two aio requests, A and B both for the same socket, can I be sure
> that they will complete in the order that I submit them ? Can I also
> be sure that parts of the I/O request for A will not be mixed up with
> B ? Will that still be true if one of the requests is aio and one a "normal"
> send/recvmsg() for example ?
The POSIX standard does not seem to require any ordering between requests,
and some implementations take advantage of this by using threads to execute
requests. That said, providing intra request ordering for sockets is easy
to do, and is one of the guarantees I'm trying to make as it allows the
implementation to provide the same semantics as are required for things
like zero copy tx.
-ben
--
"Do you seek knowledge in time travel?"
next prev parent reply other threads:[~2002-10-11 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 22:35 [patch] add iocb to network protocols Benjamin LaHaise
2002-10-10 23:22 ` David S. Miller
2002-10-10 23:40 ` Benjamin LaHaise
2002-10-10 23:36 ` David S. Miller
2002-10-11 20:15 ` kuznet
2002-10-11 20:24 ` Benjamin LaHaise
2002-10-11 9:31 ` Steven Whitehouse
2002-10-11 10:27 ` Benjamin LaHaise [this message]
2002-10-12 1:21 ` David S. Miller
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=20021011062709.A14784@redhat.com \
--to=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=steve@gw.chygwyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).