From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <efdc7fb80faff207dd6a1a65536f084d@felloff.net>
Date: Sun, 14 Sep 2014 12:49:32 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDE8C922-88C2-465B-A01F-3674E3AD7C4A@ar.aichi-u.ac.jp>
References: <efdc7fb80faff207dd6a1a65536f084d@felloff.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] segattach in telnetd
Topicbox-Message-UUID: 165abec6-ead9-11e9-9d60-3106f5b1d025

Hello,

I think=20
	vastart +=3D 2*1024*1024;=20
is weird.
if we look /proc/$ip/segment in share(), we will have better solution.
but I am not convinced we should apply the solution.
because we seldom needs shared segment.

I haven=E2=80=99t had any trouble with telnetd.
I needed shared segment for special purpose in my program (Pegasus).

thanks

2014/09/14 12:17=E3=80=81cinap_lenrek@felloff.net =E3=81=AE=E3=83=A1=E3=83=
=BC=E3=83=AB=EF=BC=9A

> why? segattach() gets an explicit address here and
> it should round va down and va+len up as neccesary
> to make them page aligned. but the initial passed
> range should be covered by the created segment
> in any case.
>=20
> do you have any trouble with telnet that is fixed
> by your change?
>=20
> --
> cinap
>=20