From: "Rémi Denis-Courmont" <remi@remlab.net>
To: "Sjur Brændeland" <sjurbren@gmail.com>
Cc: netdev@vger.kernel.org, Alexey Orishko <alexey.orishko@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1.
Date: Mon, 5 Dec 2011 17:46:14 +0200 [thread overview]
Message-ID: <201112051746.18180.remi@remlab.net> (raw)
In-Reply-To: <CAJK669ZhM_KSOd0MS7jTVvJ16KqNzPCj-Ns1ytN5NPg5PxgoOQ@mail.gmail.com>
Le lundi 5 décembre 2011 16:33:50 Sjur Brændeland, vous avez écrit :
> Hi Rémi,
>
> > It's even weirder then. If you have control over both ends and the NCM
> > 1.0 interface is not adequate, then you really should use your own CDC
> > class for the purpose.
>
> The reason we use NCM is performance: CDC normally gives less than 100Mbps,
> while NCM can give you up to 200Mbps.
NCM is a sub-profile of CDC, so that statement makes no sense to me.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2011-12-05 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 20:44 [RFC 0/3] caif: Add support for CAIF over CDC NCM USB interface Sjur Br��ndeland
2011-11-30 20:44 ` [RFC 1/3] caif: Add support for flow-control on device's tx-queue Sjur Br��ndeland
2011-11-30 20:44 ` [RFC 2/3] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1 Sjur Br��ndeland
2011-12-01 7:13 ` Rémi Denis-Courmont
2011-12-05 13:14 ` Sjur Brændeland
2011-12-05 14:03 ` Rémi Denis-Courmont
2011-12-05 14:33 ` Sjur Brændeland
2011-12-05 15:46 ` Rémi Denis-Courmont [this message]
2011-11-30 20:44 ` [RFC 3/3] caif: Add support for CAIF over CDC NCM USB interface Sjur Br��ndeland
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=201112051746.18180.remi@remlab.net \
--to=remi@remlab.net \
--cc=alexey.orishko@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sjurbren@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.