On Thu, 01 Apr 2010 09:54:54 -0700 Chandra Seetharaman <sekharan@xxxxxxxxxx> wrote: > > 1. The purpose of multiple tgtds (and the control port) is to make each > tgtd dedicated to ipaddress (or port). > > 2. Each target will be associated with only one ip address (which also > means we have to add a ip address token to target definition). > > (1) and (2) make me think that we do not need an explicit "control port" > parameter for targets.conf syntax. > > If any target has a ip address specifically defined, then tgt-admin can > define a control port and use it at the right place (as it does with tid > currently) and keep the control port definition totally internal to > tgt-admin. Yeah, we could generate 'control port' from 'iscsi ip address (or port)'. However, tgt needs to support more than iSCSI. > Does it make sense ? Or am I missing something ? > > I had a related question, will we ever want to make multiple ip > addresses served by a single tgtd ? Yeah, by default, tgtd accepts any ip addresses of the host. Can can change this behavior with 'portal' option. -- 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
