From: Cong Wang <xiyou.wangcong@gmail.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
netdev-owner@vger.kernel.org
Subject: Re: [PATCH net-next 02/10] vxlan: handle skb_clone failure
Date: Thu, 6 Jun 2013 08:47:49 +0800 [thread overview]
Message-ID: <CAM_iQpX-RY585=DszU7dURFSFKNhcyDcVLVqDrTxtLep1o_8vw@mail.gmail.com> (raw)
In-Reply-To: <OF0B8CEFF8.C94A266F-ON85257B81.004D331F-85257B81.004D7015@us.ibm.com>
On Wed, Jun 5, 2013 at 10:05 PM, David Stevens <dlstevens@us.ibm.com> wrote:
> netdev-owner@vger.kernel.org wrote on 06/05/2013 02:59:56 AM:
>
>> From: Cong Wang <xiyou.wangcong@gmail.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?
next prev parent reply other threads:[~2013-06-06 0:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 4:24 [PATCH net-next 01/10] vxlan: only migrate dynamic FDB entries Stephen Hemminger
2013-06-05 4:24 ` [PATCH net-next 02/10] vxlan: handle skb_clone failure Stephen Hemminger
2013-06-05 6:59 ` Cong Wang
2013-06-05 14:05 ` David Stevens
2013-06-06 0:47 ` Cong Wang [this message]
2013-06-06 1:31 ` Stephen Hemminger
2013-06-05 12:50 ` David Stevens
2013-06-05 4:24 ` [PATCH net-next 03/10] vxlan: move IGMP join/leave to work queue Stephen Hemminger
2013-06-05 6:47 ` Cong Wang
2013-06-05 7:29 ` Mike Rapoport
2013-06-05 8:00 ` Cong Wang
2013-06-05 15:41 ` Stephen Hemminger
2013-06-08 8:23 ` Mike Rapoport
2013-06-05 15:42 ` Stephen Hemminger
2013-06-06 0:49 ` Cong Wang
2013-06-05 15:37 ` [PATCH net] vxlan: fix crash on module removal Stephen Hemminger
2013-06-06 1:11 ` Cong Wang
2013-06-06 1:32 ` Stephen Hemminger
2013-06-05 4:24 ` [PATCH net-next 04/10] vxlan: send notification when MAC migrates Stephen Hemminger
2013-06-05 4:24 ` [PATCH net-next 05/10] vxlan: make vxlan_xmit_one void Stephen Hemminger
2013-06-05 12:54 ` David Stevens
2013-06-05 4:24 ` [PATCH net-next 06/10] vxlan: convert remotes list to list_rcu Stephen Hemminger
2013-06-05 4:24 ` [PATCH net-next 07/10] vxlan: port module param should be ushort Stephen Hemminger
2013-06-05 13:35 ` Sergei Shtylyov
2013-06-05 4:24 ` [PATCH net-next 08/10] vxlan: use initializer for dummy structures Stephen Hemminger
2013-06-05 4:24 ` [PATCH net-next 09/10] vxlan: whitespace cleanup Stephen Hemminger
2013-06-05 12:55 ` David Stevens
2013-06-05 4:24 ` [PATCH net-next 10/10] vxlan: version 0.2 Stephen Hemminger
2013-06-05 6:23 ` [PATCH net-next 01/10] vxlan: only migrate dynamic FDB entries Cong Wang
2013-06-06 23:16 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM_iQpX-RY585=DszU7dURFSFKNhcyDcVLVqDrTxtLep1o_8vw@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).