From owner-freebsd-hackers Thu Jan 21 02:39:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17319 for freebsd-hackers-outgoing; Thu, 21 Jan 1999 02:39:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17312 for ; Thu, 21 Jan 1999 02:39:29 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-smtp (Exim 2.054 #1) id 103FPB-0001nL-00; Thu, 21 Jan 1999 14:23:57 +0600 Date: Thu, 21 Jan 1999 14:23:57 +0600 (ALMT) From: Boris Popov To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Two bugs and suggestion for IPX stack In-Reply-To: <199901210703.XAA06685@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Mike Smith wrote: > > Do you have more changes as part of your ongoing work, or should we > commit these immediately to simplify your work? These patches are minimal to make IPX usable for applications. One patch that not submited, change structure of sockaddr_ipx: struct sockaddr_ipx { u_char sipx_len; u_char sipx_family; struct ipx_addr sipx_addr; - char sipx_zero[2]; + u_char sipx_pt; + char sipx_zero; }; New field sipx_pt should be filled in ipx_input() subroutine. There is also ability to pass it to ipx_output(), but it can affect existing applications. That helps to deal with IPX packet types without involving SO_HEADERS_ON_INPUT. With that, there is no additional patches. So if introducing sipx_pt is correct, I can send this patch to commit with others. > > BTW, I mostly finish work on Netware client (typical throughput > > about 730Kb/s on 10Mbit network). Higher rates is possible with packet > > burst mode, so does any body know the details ? > > I can't help you with the details there, sorry. Are you going to be > able to release this code for us to use? We'd be very happy indeed to > see this available; anything else we can do to help? Of course, I will release this code next week (if nothing serious happens :). And if someone can review and test fs part of code (it should have _enough_ bugs, especially for paged IO) that will be very helpfull. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message