Subject: uimove() uses int for size ?
To: None <tech-kern@netbsd.org>
From: Carlo Micera <miceracar@iol.it>
List: tech-kern
Date: 01/02/2000 11:58:12
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01BF5518.A5342FA0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi,
why does uiomove() take int as the size parameter ? Shouldn't it be =
size_t or
something ? This isn't probably much significant, as using
int means that the move is limited to 2GB on 32bit archs and this
is much more than kernel is able to map anyway ...
Jaromir
------=_NextPart_000_0007_01BF5518.A5342FA0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Hi,</DIV>
<DIV>why does uiomove() take int as the size parameter ? Shouldn't it be =
size_t=20
or</DIV>
<DIV>something ? This isn't probably much significant, as using</DIV>
<DIV>int means that the move is limited to 2GB on 32bit archs and =
this</DIV>
<DIV>is much more than kernel is able to map anyway ...</DIV>
<DIV> </DIV>
<DIV>Jaromir</DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0007_01BF5518.A5342FA0--