From: David Miller <davem@davemloft.net>
To: ubraun@linux.vnet.ibm.com
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 04:59:44 -0800 (PST) [thread overview]
Message-ID: <20100112.045944.197636957.davem@davemloft.net> (raw)
In-Reply-To: <1263299131.6037.44.camel@braunu-laptop>
From: Ursula Braun <ubraun@linux.vnet.ibm.com>
Date: Tue, 12 Jan 2010 13:25:31 +0100
> Sounds like a good idea, but there exists a qeth-specific problem if
> sniffer configuration should be switched to ethtool: Ethtool requires
> the existence of the network interface for the network device. The
> network interface for s390 network devices is defined within an
> s390-specific initialization step called "online setting". The sniffing
> characteristic must be configured before the online setting of the
> device, since NTA-specific initialization steps are necessary. At that
> point of time we cannot make use of ethtool, because the network
> interface name is not known yet. That means switching to your proposed
> ethtool-based configuration mechanism for HS NTA would result in an
> additional major rework of qeth device setup.
If you have a place to stick sysfs nodes, you've obviously
instantiated the device already.
next prev parent reply other threads:[~2010-01-12 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 11:19 [patch 1/3] [PATCH] qeth: HiperSockets Network Traffic Analyzer Ursula Braun
2010-01-12 11:23 ` David Miller
2010-01-12 12:25 ` Ursula Braun
2010-01-12 12:59 ` David Miller [this message]
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=20100112.045944.197636957.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=frank.blaschka@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).