Stefan Richter wrote:
> Bernhard Kaindl wrote:
>> The biggest block size that worked here was 2048 bytes, which was
>> enough to get nearly 10MB/s of data transfer rate from the remote
>> memory to disk.
>
> The maximum payload size of block requests depends on three things:
> 1. speed of the connection between the two nodes (debugged machine and
> debugging machine), 2. link layer controllers of the two nodes, 3.
> software on the debugging machine.
>
> 1.) S100: 512 bytes, S200: 1024 bytes, S400: 2048 bytes, S800 and more:
> 4096 bytes.
PS:
If there are only 1394a nodes, you can read the connection speed from
the speed map registers on the debugging machine. It becomes difficult
for 1394b nodes and some mixtures of 1394a and b nodes. But consumer
1394b hardware is always S800 capable. Consumer 1394a hardware is
always S400 capable. Except consumer camcorders which are AFAIK
typically limited to S100, but they have only one port and will
therefore never sit between debugging and debugged PC. So it's not as
difficult in 99.9% of the cases: You can expect S400, some people might
get S800. But you can't use the bigger S800 block size if the debugging
machine runs ohci1394.
> 2.) Controllers on CardBus cards are limited to 1024 bytes payload of
> asynchronous packets, for reasons I don't know. The other available
> controllers only have the above mentioned speed-dependent limit.
This is relevant if the debugging or the debugged PC have a CardBus
card. Actually this is the limit of all 1394a CardBus card I have seen;
I don't know about 1394b CardBus cards, or Express cards. (I suppose
Express cards have no limits of this kind, as they are just PCIe cards
in a different formfactor.)
This payload limitation of the link can be read from the bus info blocks
of the debugged and the debugging machine. Though I am not entirely
sure right now if the ohci1394_earlyinit driven machine will have its
bus info block properly set up.
--
Stefan Richter
-=====-=-=== ==-- --=--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]