[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 Jun 2013 18:31:18 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: David Stevens <dlstevens@...ibm.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
netdev-owner@...r.kernel.org
Subject: Re: [PATCH net-next 02/10] vxlan: handle skb_clone failure
On Thu, 6 Jun 2013 08:47:49 +0800
Cong Wang <xiyou.wangcong@...il.com> wrote:
> On Wed, Jun 5, 2013 at 10:05 PM, David Stevens <dlstevens@...ibm.com> wrote:
> > netdev-owner@...r.kernel.org wrote on 06/05/2013 02:59:56 AM:
> >
> >> From: Cong Wang <xiyou.wangcong@...il.com>
> >> If OOM, shouldn't we exit immediately instead of continue handle the
> >> next one?
> >
> > It could be a temporary condition; trying again doesn't really hurt,
> > in case some do go through. So, I prefer this, but could live with
> > bailing for all destinations, too.
> >
>
> The problem we don't know if it is temporary or not, unless mm provides
> EAGAIN?
> --
> 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
There is no EAGAIN in the network transmit path, it is not called from
user context.
--
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