All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Licquia <licquia@progeny.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Fwd: Weird ia64 problem]
Date: Wed, 05 Oct 2005 22:13:05 +0000	[thread overview]
Message-ID: <1128550385.4623.52.camel@laptop1> (raw)
In-Reply-To: <1128548614.4623.45.camel@laptop1>

On Wed, 2005-10-05 at 14:54 -0700, Luck, Tony wrote:
> >It was suggested to me that this might be of interest outside the LSB,
> >and that I should forward it more widely...
> 
> Running under strace, I see you write 2048 bytes at a time until you
> see EAGAIN.  Then you read 4096 bytes to empty the pipe a little.
> 
> Then you try to write 4120 bytes (more than you just emptied).
> 
> Is that what you are trying to do?

That sounds about right.

FWIW, if you'd like a look at the source of one of the LSB tests that's
failing, see:

http://cvs.gforge.freestandards.org/cgi-bin/cvsweb.cgi/tests/lsb-runtime-test/modules/vsx-pcts/tset/ANSI.os/streamio/fwrite/fwrite.c?rev=1.1.1.1&contenttype=text/x-cvsweb-markup&cvsroot=lsb

Look at function "test3", specifically the part after where it reports
"testing assertion using non-blocking pipe".

> Do you expect a partial write, rather than the EAGAIN?

That appears to be what's happening in most other cases, and also
appears to be what the LSB tests want.


  parent reply	other threads:[~2005-10-05 22:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 21:43 [Fwd: Weird ia64 problem] Jeff Licquia
2005-10-05 21:54 ` Luck, Tony
2005-10-05 22:09 ` Luck, Tony
2005-10-05 22:13 ` Jeff Licquia [this message]
2005-10-05 22:30 ` Jeff Licquia
2005-10-05 22:33 ` Luck, Tony
2005-10-05 23:09 ` Jeff Licquia
2005-10-05 23:28 ` Luck, Tony
2005-10-05 23:40 ` Luck, Tony
2005-10-06  1:02 ` Ian Wienand
2005-10-07 14:29 ` Jeff Licquia
2005-10-08  2:40 ` Tony Luck

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=1128550385.4623.52.camel@laptop1 \
    --to=licquia@progeny.com \
    --cc=linux-ia64@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.