lmb@vsi1.UUCP (Larry Blair) (05/15/88)
It is my understanding that the blazer buffers 30 characters when communicating
in slow mode with the interface speed locked. The only reason I can think of
for choosing this number is so that when a user in an interactive conversation
types XOFF, the sending program will stop relatively quickly. The biggest
problem with this particular value is that it is less than the largest transfer
made by uucp. This prevents me from using the blazer with the speed locked
when calling other sites without blazers (my Sun does not support hardware flow
control). It should be noted that 30 characters will be too many if two
machines are talking with flow control, and the XOFF gets sent when there is
less than 30 characters space in the receive buffer.
What is really needed here is another register where the user can specify the
number of characters to buffer. 255 should indicate unlimited (well... >10K)
buffering.
Perhaps Richard Seigal will tell me that I don't know what I'm talking about;
or, perhaps, we'll see this in rev. 4.1.
--
* * O Larry Blair
* * O VICOM Systems Inc. sun!pyramid----\
* * O 2520 Junction Ave. uunet!ubvax----->!vsi1!lmb
* * O San Jose, CA 95134 ucbvax!tolerant/
* * O +1-408-432-8660lmb@vsi1.UUCP (Larry Blair) (05/19/88)
I'd like to thank all the people who sent me email clearing up my
misconceptions regarding Trailblazer buffering. The gist of those
messages were that the 'blazer will buffer up to 2K if the interface
speed is locked and no flow control is specified.
I would still like to see a register selectable buffering size (for
when flow control is specified), so that the size can be reduced,
when necessary.
--
* * O Larry Blair
* * O VICOM Systems Inc. sun!pyramid----\
* * O 2520 Junction Ave. uunet!ubvax----->!vsi1!lmb
* * O San Jose, CA 95134 ucbvax!tolerant/
* * O +1-408-432-8660