9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs error msg: didn't like (1460 274) byte message
Date: Wed, 25 Sep 2002 23:12:26 +0200	[thread overview]
Message-ID: <200209252112.g8PLCQ429043@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 25 Sep 2002 14:24:23 -0400." <a14e85571895b8ff58bc08d27aa878ae@plan9.bell-labs.com>

(added the same syslog debugging and)
Tried it. Works exactly like one of my previous attempts (acc. to debug log).
Works fine until it encounters a message with size=152;
then it seems that 'n = GBIT32(buf)' doesn't do what we need;
it in the next read it tries to read (n=-104)-4 bytes and fails.
Would be nice if we could use read9pmsg (all these problems solved
in one place). But then we need a solution for the varying message size.

Axel.

> The problem is the buffer can be arbitrarily sized, though
> typically 8192+IOHDRSZ is the max a client and server will
> agree on.  Cpu uses a much larger max size to improve graphics
> performance.
>
> Here's a fixed xfer9p.  I forgot that the initial count
> includes itself.


  parent reply	other threads:[~2002-09-25 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 18:24 Russ Cox
2002-09-25 18:44 ` Axel Belinfante
2002-09-25 21:12 ` Axel Belinfante [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-25 21:30 Russ Cox
2002-09-26  8:49 ` Axel Belinfante
2002-09-25 21:21 Russ Cox
2002-09-24 23:42 Russ Cox
2002-09-25 11:45 ` Axel Belinfante
2002-09-25 18:19 ` Axel Belinfante
2002-09-24 23:25 Axel Belinfante

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=200209252112.g8PLCQ429043@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).