From: Jiri Benc <jbenc@redhat.com>
To: Naveen <dear.chap@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Delivery Status Notification (Failure)
Date: Thu, 24 Sep 2015 15:09:06 +0200 [thread overview]
Message-ID: <20150924150906.067bba62@griffin> (raw)
In-Reply-To: <CAOLDph0pO0q3A4-mRjn3wkGvHP5c9anBWbaDBDOLhVRz+JVDMQ@mail.gmail.com>
On Thu, 24 Sep 2015 08:03:39 -0400, Naveen wrote:
> Right now the only way to detect if an interface has a peer(veth)
> is touse ethtool -S. Instead I was thinking of adding it to device
> attributes as a peer_ifndex entry. In drivers/net/veth.c I could add
> an entry to
> dev->groups for a veth specific group. Would that be acceptable ?
Recent kernels announce the peer in IFLA_LINK, including its netnsid
(thus it's finally possible to track peers across net namespaces).
Just try "ip a" with a recent kernel.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-09-24 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <047d7b5dbb76a0065405207cfe24@google.com>
2015-09-24 12:03 ` Fwd: Delivery Status Notification (Failure) Naveen
2015-09-24 12:50 ` Andy Gospodarek
2015-09-24 13:09 ` Jiri Benc [this message]
2004-07-11 6:06 adsadnbs
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=20150924150906.067bba62@griffin \
--to=jbenc@redhat.com \
--cc=dear.chap@gmail.com \
--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).