From: Ursula Braun <ubraun@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
frank.blaschka@de.ibm.com, ursula.braun@de.ibm.com
Subject: Re: [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer
Date: Tue, 12 Jan 2010 12:19:44 +0100 [thread overview]
Message-ID: <1263295184.6037.26.camel@braunu-laptop> (raw)
On Tue, 2010-01-12 at 01:30 +0100, David Miller wrote:
> From: frank.blaschka@de.ibm.com
> Date: Mon, 11 Jan 2010 13:50:50 +0100
>
> > From: Ursula Braun <ursula.braun@de.ibm.com>
> >
> > New feature to trace HiperSockets network traffic for debugging
> > purposes.
> >
> > Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
> > Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
> How exactly does this work?
Dave,
HiperSockets provides internal "virtual" Local Area Networks within a
System z server for communication between different virtual servers
running on one System z server.
The HiperSockets Network Traffic Analyzer (HS NTA) is a function
available with System z10. It traces messages from and to devices within
the same HiperSockets LAN the NTA device belongs to, if the
participating LPARs are authorized for sniffing at the SE (Support
Element of a System z server).
An HS NTA device in Linux on System z is a specialized HiperSockets
device managed by the qeth driver and initialized specifically for
sniffing. The trigger for an HS device to act as a Network Traffic
Analyzer is the sysfs attribute "sniffer". If this attribute is set to
1, the NTA-specific initialization is started when the HS device is
brought online. Traffic sniffing starts, once the device is switched
into promiscuous mode, for instance by invoking the tcpdump-tool.
Regards, Ursula Braun
next reply other threads:[~2010-01-12 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 11:19 Ursula Braun [this message]
2010-01-12 11:23 ` [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer David Miller
2010-01-12 12:25 ` Ursula Braun
2010-01-12 12:59 ` David Miller
2010-01-12 13:29 ` Ursula Braun
2010-01-14 4:35 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 12:50 [patch 0/3] s390: qeth patches for 2.6.34 frank.blaschka
2010-01-11 12:50 ` [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer frank.blaschka
2010-01-12 0:30 ` 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=1263295184.6037.26.camel@braunu-laptop \
--to=ubraun@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=frank.blaschka@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ursula.braun@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox