From: frank.blaschka@de.ibm.com
To: netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 00/11] [RFC] s390: af_iucv traffic over HiperSockets transport
Date: Wed, 27 Jul 2011 18:12:42 +0200 [thread overview]
Message-ID: <20110727161242.018577444@de.ibm.com> (raw)
Following patch set implements a new feature to use HiperSockets
as a transport mechanism for the af_iucv address family. Basic
design idea is: The current transport mechanism for af_iucv (iucv)
is only available on VM. HiperSockets provide similar capabilities
as iucv and are available on LPAR. There is guaranty for data
integrity, in order delivery and delivery acknowledgment. A new
HiperSockets feature is exploited to support
flow control/congestion management. For this it is nearby to extend
af_iucv address family to use HiperSockets transport.
shortlog:
Einar Lueck (4)
qdio: support asynchronous delivery of storage blocks
qdio: support forced signal adapter indications
qeth: exploit asynchronous delivery of storage blocks
qeth: support forced signal adapter indications
Ursula Braun (3)
iucv: kernel option for z/VM IUCV and HiperSockets
af_iucv: cleanup - use iucv_sk(sk) early
af_iucv: add HiperSockets transport
Frank Blaschka (4)
iucv: introduce loadable iucv interface
af_iucv: use loadable iucv interface
if_ether: add new Ethernet Protocol ID for af_iucv
qeth: add support for af_iucv HiperSockets transport
Thanks for review and comments,
Frank
next reply other threads:[~2011-07-27 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 16:12 frank.blaschka [this message]
2011-07-27 16:12 ` [patch 01/11] [PATCH] iucv: introduce loadable iucv interface frank.blaschka
2011-07-27 23:29 ` David Miller
2011-07-28 4:13 ` Frank Blaschka
2011-07-28 5:10 ` David Miller
2011-07-27 16:12 ` [patch 02/11] [PATCH] iucv: kernel option for z/VM IUCV and HiperSockets frank.blaschka
2011-07-27 16:12 ` [patch 03/11] [PATCH] af_iucv: use loadable iucv interface frank.blaschka
2011-07-27 16:12 ` [patch 04/11] [PATCH] af_iucv: cleanup - use iucv_sk(sk) early frank.blaschka
2011-07-27 16:12 ` [patch 05/11] [PATCH] if_ether: add new Ethernet Protocol ID for af_iucv frank.blaschka
2011-07-27 16:12 ` [patch 06/11] [PATCH] af_iucv: add HiperSockets transport frank.blaschka
2011-07-27 16:12 ` [patch 07/11] [PATCH] qdio: support asynchronous delivery of storage blocks frank.blaschka
2011-07-27 16:12 ` [patch 08/11] [PATCH] qdio: support forced signal adapter indications frank.blaschka
2011-07-27 16:12 ` [patch 09/11] [PATCH] qeth: " frank.blaschka
2011-07-27 16:12 ` [patch 10/11] [PATCH] qeth: exploit asynchronous delivery of storage blocks frank.blaschka
2011-07-27 16:12 ` [patch 11/11] [PATCH] qeth: add support for af_iucv HiperSockets transport frank.blaschka
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=20110727161242.018577444@de.ibm.com \
--to=frank.blaschka@de.ibm.com \
--cc=linux-s390@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).