[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091112110921.07a8412d@nehalam>
Date: Thu, 12 Nov 2009 11:09:21 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: Ed Cashin <ecashin@...aid.com>
Cc: ecashin@...aid.com, karaluh@...aluh.pl, roel.kluin@...il.com,
harvey.harrison@...il.com, bzolnier@...il.com,
netdev@...r.kernel.org
Subject: Re: [PATCH 04/10] AOE: use rcu to find network device
On Thu, 12 Nov 2009 13:07:35 -0500
Ed Cashin <ecashin@...aid.com> wrote:
> Thanks for the responses.
>
> On Thu Nov 12 12:11:12 EST 2009, shemminger@...tta.com wrote:
> ...
> > Since it is emulating a block device, why not propgate error back
> > up the stack like a disk that's offline.
>
> The lack of local interfaces to use for AoE might be temporary. For
> example, the admin might be loading a new network driver, or a new
> link might go online through which the AoE target can be reached.
>
> If AoE command packets are not sent or resent but instead are
> effectively dropped while there are no local interfaces through which
> to send, then the AoE commands will timeout through the normal
> mechanisms, at which time the error will be signaled to the block
> layer. It will be like normal unreliable ethernet transport.
>
> In the common case, I think that's going to be the expected behavior,
> but a printk would probably still be helpful in case the admin doesn't
> realize why the AoE device is timing out.
>
Okay, you might want to ratelimit the printk
--
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists