Date: Sun, 4 Nov 2007 22:57:44 -0800 (PST) From: Tom Samplonius <tom@samplonius.org> To: James Mansion <james@mansionfamily.plus.com> Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI in 7.0 Message-ID: <11986784.3811194245864164.JavaMail.root@ly.sdf.com> In-Reply-To: <472C458E.1060309@mansionfamily.plus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- "James Mansion" <james@mansionfamily.plus.com> wrote: > Have to say I was very pleasntly shocked to see iSCSI initiator > support > in the 7.0 overview. > > Is this the right place to ask about it? > > Specifically, does FreeBSD ensure that socket buffers are allocated > from > a set-aside pool > for iSCSI data, so that iSCSI can be used for swap in a diskless > environment? (Perhaps > ideally it would be a mount-time option for this: its only really swap Well, since it is a kernel mode driver, it has to be use kernel memory. There should be no issue with a swap deadlock, because the iSCSI client can't get more memory until some memory is swapped in. But FreeBSD does not generally like running out kernel memory either. > that needs it after all) > > Linux fails to do this for iSCSI or AoE or nbd and prone (perhaps > theoretically prone, > but its a worry) to deadlock when swapping over the network. I think Linux is using a kernel mode driver too. Well, there were several iSCSI clients when I checked. I'm not sure which you are looking at. > Also, is the framework support such that it could be extended to > support > coraid AoE or > simple nbd like Linux, but without the limitation above? Well, FreeBSD has ggated for ndb like things. It has been around for a while. AoE sounds completely retarded. I hope it disappears before people think it is actually something serious. > Thanks > James Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11986784.3811194245864164.JavaMail.root>