From: David Miller <davem@davemloft.net>
To: shengyong1@huawei.com
Cc: netdev@vger.kernel.org, yangyingling@huawei.com,
steffen.klassert@secunet.com, hannes@redhat.com
Subject: Re: Question: should local address be expired when updating PMTU?
Date: Mon, 02 Feb 2015 13:31:53 -0800 (PST) [thread overview]
Message-ID: <20150202.133153.1075396169633961300.davem@davemloft.net> (raw)
In-Reply-To: <54CF3348.40207@huawei.com>
From: shengyong <shengyong1@huawei.com>
Date: Mon, 2 Feb 2015 16:20:24 +0800
> Hi, David Miller
There are other people on this list more skilled than I am at answering
this question, just FYI...
next prev parent reply other threads:[~2015-02-02 21:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 8:20 Question: should local address be expired when updating PMTU? shengyong
2015-02-02 21:31 ` David Miller [this message]
2015-02-03 0:52 ` Alex Gartrell
2015-02-03 0:52 ` Alex Gartrell
2015-02-03 1:28 ` shengyong
2015-02-03 1:28 ` shengyong
2015-02-03 2:10 ` Calvin Owens
2015-02-03 2:10 ` Calvin Owens
2015-02-03 3:21 ` shengyong
2015-02-03 3:21 ` shengyong
2015-02-03 9:28 ` Steffen Klassert
2015-02-03 10:54 ` shengyong
2015-02-03 12:01 ` Steffen Klassert
2015-02-04 1:59 ` shengyong
2015-02-05 7:21 ` Steffen Klassert
2015-02-27 2:37 ` shengyong
2015-02-27 10:32 ` Steffen Klassert
2015-03-30 10:32 ` Steffen Klassert
2015-03-30 10:33 ` [PATCH RFC 1/3] ipv6: Fix after pmtu events dissapearing host routes Steffen Klassert
2015-03-30 11:15 ` Sheng Yong
2015-03-30 18:24 ` Martin Lau
2015-04-01 8:09 ` Steffen Klassert
2015-03-30 10:33 ` [PATCH RFC 2/3] ipv6: Extend the route lookups to low priority metrics Steffen Klassert
2015-03-30 10:34 ` [PATCH RFC 3/3] ipv6: Don't update pmtu on uncached routes Steffen Klassert
2015-03-30 11:13 ` Question: should local address be expired when updating PMTU? Sheng Yong
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=20150202.133153.1075396169633961300.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shengyong1@huawei.com \
--cc=steffen.klassert@secunet.com \
--cc=yangyingling@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.