Andriy Gapon wrote:
> on 10/12/2010 16:45 Alexander Motin said the following:
>> by default. Many SCSI drivers still limited by DFLTPHYS - 64K.
>
> Including the cases where MAXBSIZE is abused because it historically has the
> same
> value.
DFLTPHYS automatically assumed by CAM for all SIMs not
on 10/12/2010 16:45 Alexander Motin said the following:
> by default. Many SCSI drivers still limited by DFLTPHYS - 64K.
Including the cases where MAXBSIZE is abused because it historically has the
same
value.
--
Andriy Gapon
___
freebsd-hackers@freeb
Hello, Andriy.
You wrote 10 декабря 2010 г., 18:03:27:
> on 10/12/2010 16:48 Andriy Gapon said the following:
>> But maybe I misunderstood your question and you talked about a different I/O
>> layer
>> or different I/O path.
> Oh, probably you talk about physread/physwrite == physio.
> Indeed, it
Hello, Alexander.
You wrote 10 декабря 2010 г., 17:45:20:
>>I'm digging thought GEOM/IO code and can not find place, where
>> requests from userland to read more than MAXPHYS bytes, is splitted
>> into several "struct bio"?
>> It seems, that these children request are issued o
on 10/12/2010 16:48 Andriy Gapon said the following:
> But maybe I misunderstood your question and you talked about a different I/O
> layer
> or different I/O path.
>
Oh, probably you talk about physread/physwrite == physio.
Indeed, it issues bio-s with max size of si_iosize_max and runs them
s
on 10/12/2010 15:22 Lev Serebryakov said the following:
> Hello, Freebsd-geom.
>
>I'm digging thought GEOM/IO code and can not find place, where
> requests from userland to read more than MAXPHYS bytes, is splitted
> into several "struct bio"?
Check out g_disk_start().
The split is
Lev Serebryakov wrote:
>I'm digging thought GEOM/IO code and can not find place, where
> requests from userland to read more than MAXPHYS bytes, is splitted
> into several "struct bio"?
>
> It seems, that these children request are issued one-by-one, not in
> parallel, am
Hello, Freebsd-geom.
I'm digging thought GEOM/IO code and can not find place, where
requests from userland to read more than MAXPHYS bytes, is splitted
into several "struct bio"?
It seems, that these children request are issued one-by-one, not in
parallel, am I right? Wh
8 matches
Mail list logo