From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: PPP Date: 23 Oct 2002 15:18:50 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1035375369.2229.51.camel@cool> References: <20021022161733.2170.qmail@web14702.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YkOKOQLk8uofP3ADNs69" Return-path: In-Reply-To: <20021022161733.2170.qmail@web14702.mail.yahoo.com> List-Id: To: Pooja Nagpal Cc: Linux-8086 --=-YkOKOQLk8uofP3ADNs69 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > Hi! >=20 > Sorry for the slow replies! >=20 > I had something like interrupts(like Blaz Antonic suggested) in mind inst= ead of polling.=20 >=20 > I was also wondering what would happen if packets came in faster than we = can process. Will i lose > the packets.When I tested the PPP code in Linux before trying it on ELKS,= I somehow seemed to be > getting empty frames etc. The same code when complied for ELKS worked fin= e. I am not sure what the > problem was.=20 >=20 > I don't think the options negotiated in the LCP are 'do and forget'. I th= ink the link properties > need to stored. pppd could just negotiate options, store and exit. The ne= twork layer specific NCP > could then take over but I am not sure where it goes. If its in the kerne= l, how should i go about > it? >=20 > Thanks, > Pooja >=20 I just had a glance to the PPP rfc and it seems that in order to have a functional PPP, LCP NCP packets should be interpretted all times. The straightforward way of doing it is to have a pppd demon reading the packets from the serial line doing the processing and passing it to the above layer. For ipv4 in ELKS this means passing them to the ktcp demon. This passing is that conserns me. This will probably be done throught a UNIX socket. So for a process to get it's data we need many many task switches and data copying(kernel -> pppd -> kernel -> ktcp -> kernel -> process). So it is probably better for the PPP code and ipv6 code to be added in ktcp. Harry --=-YkOKOQLk8uofP3ADNs69 Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9tpMJXrjIZPA34x8RArmlAKCkI3fMimk4SHWjEOUU2Zog33yJ6ACcDwYN R7FklW8r8FH0yYURJuHUo+E= =DQoH -----END PGP SIGNATURE----- --=-YkOKOQLk8uofP3ADNs69--