On Wed, 2012-04-18 at 12:42 -0500, Mike Christie wrote:
On 04/18/2012 11:58 AM, Eddie Wai wrote:
On Wed, 2012-04-18 at 03:14 -0500, Mike Christie wrote:
On 04/18/2012 01:21 AM, Eddie Wai wrote:
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
struct msg_req_path {
uint32_thost_no;
+ uint32_tiface_num;
} req_path;
Are you using this in iscsiuo now? Do
On 04/18/2012 01:21 AM, Eddie Wai wrote:
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
struct msg_req_path {
uint32_thost_no;
+ uint32_tiface_num;
} req_path;
On Wed, 2012-04-18 at 03:14 -0500, Mike Christie wrote:
On 04/18/2012 01:21 AM, Eddie Wai wrote:
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
struct msg_req_path {
uint32_thost_no;
+
On 04/18/2012 11:58 AM, Eddie Wai wrote:
On Wed, 2012-04-18 at 03:14 -0500, Mike Christie wrote:
On 04/18/2012 01:21 AM, Eddie Wai wrote:
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
struct msg_req_path {
On 04/18/2012 12:42 PM, Mike Christie wrote:
On 04/18/2012 11:58 AM, Eddie Wai wrote:
On Wed, 2012-04-18 at 03:14 -0500, Mike Christie wrote:
On 04/18/2012 01:21 AM, Eddie Wai wrote:
On Tue, 2012-04-17 at 21:36 -0500, Mike Christie wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
On 04/04/2012 06:39 PM, Eddie Wai wrote:
struct msg_req_path {
uint32_thost_no;
+ uint32_tiface_num;
} req_path;
Are you using this in iscsiuo now? Do you match the host_no + iface_num
to some iface file in
For HBAs that can support multiple sets of network parameters, it would be
beneficial to pass the iface-iface_num handle to the corresponding
ep_connect call. This will allow the respective low level drivers to
have a way to decipher the particular set of network parameters to use for
the
