From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200209252112.g8PLCQ429043@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] fs error msg: didn't like (1460 274) byte message In-reply-to: Your message of "Wed, 25 Sep 2002 14:24:23 -0400." References: From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29037.1032988346.1@zamenhof.cs.utwente.nl> Date: Wed, 25 Sep 2002 23:12:26 +0200 Topicbox-Message-UUID: f4d6c136-eaca-11e9-9e20-41e7f4b1d025 (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.