Re: Importing iSCSI target from NetBSD

Scott,

It seems that you aren't aware that Intel/NetBSD implementation is completely userland one and it uses any block device/file as backing store (no interaction with CAM). Therefore, it won't interfere with whatever work you and others do in the CAM area.

-Maxim

Scott Long wrote:
Maxim Sobolev wrote:

Hi,

I wonder if anybody has any objections to importing iSCSI target daemon from NetBSD (Intel) into the base.

-Maxim

Yes. I'm nearing completion of locking CAM, and adding new subsystems is not going
to help that effort at the moment. I'd also like you to talk with Matt Jacob and Nate Lawson
about it since they have quite a bit of current experience with the SCSI target side of things.
So in other words, a drive-by commit is not welcome and will be drive-by uncommitted unless
you work with the people who can provide help and guidance.

Scott

_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Importing iSCSI target from NetBSD
    ... It seems that you aren't aware that Intel/NetBSD implementation is completely userland one and it uses any block device/file as backing store (no interaction with CAM). ... I've wanted to play with iSCSI targets on FreeBSD but have lacked the requisite test equipment. ... a drive-by commit is not welcome and will be drive-by uncommitted unless ...
    (freebsd-current)
  • Re: Importing iSCSI target from NetBSD
    ... It seems that you aren't aware that Intel/NetBSD implementation is completely userland one and it uses any block device/file as backing store (no interaction with CAM). ...
    (freebsd-current)