netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Rémi Denis-Courmont" <remi.denis-courmont@nokia.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] Phonet: improve documentation
Date: Wed, 24 Sep 2008 08:45:48 -0700	[thread overview]
Message-ID: <48DA60AC.5030903@oracle.com> (raw)
In-Reply-To: <200809241515.06378.remi.denis-courmont@nokia.com>

Rémi Denis-Courmont wrote:
> Fix grammar errors spotted by Randy Dunlap,
> and adds some more details.

Um, let me try again, please.

> Signed-off-by: Remi Denis-Courmont <remi.denis-courmont@nokia.com>
> ---
>  Documentation/networking/phonet.txt |   32 +++++++++++++++++++++-----------
>  1 files changed, 21 insertions(+), 11 deletions(-)
> 
> diff --git a/Documentation/networking/phonet.txt b/Documentation/networking/phonet.txt
> index f3c72e0..1506c31 100644
> --- a/Documentation/networking/phonet.txt
> +++ b/Documentation/networking/phonet.txt
> @@ -21,7 +21,7 @@ depending on the device, such as:
>  Packets format
>  --------------
>  
> -Phonet packet have a common header as follow:
> +Phonet packets have a common header as follow:

                                          follows:

>  
>    struct phonethdr {
>      uint8_t  pn_media;  /* Media type (link-layer identifier) */
> @@ -33,14 +33,17 @@ Phonet packet have a common header as follow:
>      uint8_t  pn_sobj;   /* Sender object ID */
>    };
>  
> -The device ID is split: the 6 higher order bits consitutes the device
> -address, while the 2 lower order bits are used for multiplexing, as are
> -the 8-bits object identifiers. As such, Phonet can be considered as a
> +On Linux, the link-layer header includes the pn_media byte (see below).
> +The next 7 bytes are part of the network-layer header.
> +
> +The device ID is split: the 6 higher order-bits consitute the device

                                 higher-order bits

> +address, while the 2 lower-order bits are used for multiplexing, as are
> +the 8-bit object identifiers. As such, Phonet can be considered as a
>  network layer with 6 bits of address space and 10 bits for transport
>  protocol (much like port numbers in IP world).
>  
> -The modem always has address number zero. Each other device has a its
> -own 6-bits address.
> +The modem always has address number zero. All other device have a their
> +own 6-bit address.
>  
>  
>  Link layer
> @@ -49,11 +52,18 @@ Link layer
>  Phonet links are always point-to-point links. The link layer header
>  consists of a single Phonet media type byte. It uniquely identifies the
>  link through which the packet is transmitted, from the modem's
> -perspective.
> -
> -Linux Phonet network interfaces use a dedicated link layer type
> -(ETH_P_PHONET) which is out of the Ethernet type range. They can only
> -send and receive Phonet packets.
> +perspective. Each Phonet network device shall prepend and set the media
> +type byte as appropriate. For convenience, a common phonet_header_ops
> +link-layer header operations structure is provided. It sets the
> +media type according to the network device hardware address.
> +
> +Linux Phonet network interfaces support a dedicated link layer packets
> +type (ETH_P_PHONET) which is out of the Ethernet type range. They can
> +only send and receive Phonet packets.
> +
> +The virtual TUN tunnel device driver can also be used for Phonet. This
> +requires IFF_TUN mode, _without_ the IFF_NO_PI flag. In this case,
> +there is no link-layer header, so there is no Phonet media type byte.
>  
>  Note that Phonet interfaces are not allowed to re-order packets, so
>  only the (default) Linux FIFO qdisc should be used with them.

Thanks,
~Randy

  reply	other threads:[~2008-09-24 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 15:45 [PATCH 00/11] PhoNet protocols stack v2 Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 01/11] Phonet global definitions Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 02/11] Phonet: PF_PHONET protocol family support Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 03/11] Phonet: add CONFIG_PHONET Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 04/11] Phonet: network device and address handling Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 05/11] Phonet: Netlink interface Rémi Denis-Courmont
2008-09-23 12:10   ` Thomas Graf
2008-09-24 11:30     ` Rémi Denis-Courmont
2008-09-24 13:23       ` Thomas Graf
2008-09-22 15:47 ` [PATCH 06/11] Phonet: common socket glue Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 07/11] Phonet: Phonet datagram transport protocol Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 08/11] Phonet: provide MAC header operations Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 09/11] Phonet: proc interface for port range Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 10/11] Phonet: emit errors when a packet cannot be delivered locally Rémi Denis-Courmont
2008-09-22 15:47 ` [PATCH 11/11] Phonet: kernel documentation Rémi Denis-Courmont
2008-09-23 21:43   ` Randy Dunlap
2008-09-24 12:15     ` [PATCH] Phonet: improve documentation Rémi Denis-Courmont
2008-09-24 15:45       ` Randy Dunlap [this message]
2008-09-23  3:16 ` [PATCH 00/11] PhoNet protocols stack v2 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=48DA60AC.5030903@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=remi.denis-courmont@nokia.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).