Mike,

On 01/20/2011 12:05 PM, Mike Christie wrote:
> 
> On 01/17/2011 07:15 PM, Rustad, Mark D wrote:
>> Hi all,
>>
>> I am still looking into DCBX support for iSCSI and potentially other
>> networking applications. Previously I was only considering having the
>> application be a client of the lldpad daemon, but it looks like the
>> application priority information should be available from rtnetlink.
>> Since rtnetlink is already often used by networking applications, it
>> seems like a better fit to use that interface.
> 
> Hey,
> 
> So instead of iscsid/iscsistart communicating with lldpad, they will
> use
> rtnelink to request the info or get changes?

Exactly.

>> Right now, the only missing element seems to be an rtnetlink event
>> that could be used to trigger the app to change priorities based on a
>> change in the configuration. How important do you think it is to
>> support dynamic changes to application priority? Is it essential for a
>> first implementation?
> 
> I think it will be fine if at first it does not support dynamic
> changes.
> If we will be using rtnetlink to get the initial info then there should
> not be many major changes to the iscsi tools to support dynamic
> changes.

That is the way it looks to me. I am finding that the kernel side of things is 
still kind of in flux and probably won't really be usable until 2.6.39. Using 
rtnetlink still looks like the best way to go. I also realized that isns should 
also have its priority controlled in the same manner.

-- 
Mark Rustad, [email protected]


-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to