> iscsi initiator paniced over 4 dev, and the code has limitations of
> devices, it is hardcoded to 4
>
> 9f2ae5be (scottl 2007-07-24 15:35:02 +0000 39) #define ISCSIDEV
> "iscsi"
> 9f2ae5be (scottl 2007-07-24 15:35:02 +0000 40)
> 9f2ae5be (scottl 2007-07-24 15:35:02 +0000 41) #define
> ISCSI_MAX_TARGETS 4 //64
> 9f2ae5be (scottl 2007-07-24 15:35:02 +0000 42)
> 9f2ae5be (scottl 2007-07-24 15:35:02 +0000 43) #define ISCSI_MAX_LUNS
> 4
>
> when setting this to 64, than paniced the kernel
>
get
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.4.tar.gz
but what does this have to to with the Subject:?
danny
>
> On 7/4/10, Alexander Motin <[email protected]> wrote:
> > Daisuke Aoyama wrote:
> >>>> Notes/Known Issues/Limitations:
> >>>> FreeBSD can't use transfer length > 64KB.
> >>>
> >>> Since 8.0 FreeBSD can use any transfer lengths. 64K is a safety limit
> >>> for CAM SIMs that do not report maximum transfer size. If your driver
> >>> supports bigger transactions (and even if not), you should fill maxio
> >>> field in XPT_PATH_INQ response.
> >>
> >> I set maxio=1024*1024 in version 0.2.2. As a result, the request (each
> >> ccb)
> >> have 256 blocks (128KB). I don't know why it is 128KB.
> >
> > 128KB is a default MAXPHYS value. You may rise it in your kernel if you
> > want. I am successfully using 1MB MAXPHYS now.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[email protected]"
