On Sun, Apr 17, 2011 at 5:33 PM, FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> wrote: > On Sun, 17 Apr 2011 17:23:04 +1000 > ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote: > >> Tomo, >> >> >> > Please simply reject if users specify a portal group that isn't >> > one. tgt doesn't support portal group now so no point to point non 1 >> > portal group. >> > >> >> Ok, not implementing any portal group is ok with me. > > I'm not against implementing it. But unless you implement MCS, I don't > see the point. > > >> And keeping everything as 'tgtd only supports one single portal group >> and that is #1' >> In that case, you really only ask for 'expand the portal structure to >> also keep a portal group tag but keep this hardcoded to 1' ? > > All I ask is making sure that the user interface (tgtadm) can handle > the feature. That is, make sure that if we want to support the feature > in the future, there should be no change to the exiting interface. > Ok, expand the interface to allow setting tpgt but dont change any logic. Leave the rest tpgt ignorant outside of being able to set it, but it having no effect outside of showing up in --op show. Got it. regards ronnie sahlberg -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
