From: Thomas Martitz <thomas.martitz@hhi.fraunhofer.de>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Subject: Re: Trying to implement secondary loopback
Date: Fri, 15 Mar 2013 15:35:40 +0100 [thread overview]
Message-ID: <514331BC.4080802@hhi.fraunhofer.de> (raw)
In-Reply-To: <CAFLxGvyDaaOtm1TrD-gfvhja_Uow8jtRbPyb2WcMscSLgo1umg@mail.gmail.com>
Am 15.03.2013 15:32, schrieb richard -rw- weinberger:
> On Fri, Mar 15, 2013 at 3:20 PM, Thomas Martitz
> <thomas.martitz@hhi.fraunhofer.de> wrote:
>>> The real question is, why do you need a second one?
>>> I assume your driver (for the non-existing hardware) is a ethernet driver,
>>> and now you're looking for a way to test your shiny new ethX device,
>>> correct?
>>>
>>
>> Yes. But that's only the first step. Once I have the basic ethX device
>> working I want to make sure the PCIe data transfer is working (with good
>> performance), ideally using the very same test application in user space.
>
> And there is the second loopback device is this picture?
>
Mine is the second one, as I cannot modify "lo". The standard "lo"
interface is the the first loopback and it seems to be hardcoded to be
the only one.
Best regards.
-----
visit us at
OFC 2013 / March 19-21 / Anaheim Convention Center, CA, USA / booth 11807
NABSHOW 2013 / April 8-11 / Las Vegas Convention Center, Nevada, USA / booth C7843
www.hhi.fraunhofer.de/events
next prev parent reply other threads:[~2013-03-15 14:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 12:05 Trying to implement secondary loopback Thomas Martitz
2013-03-13 11:13 ` richard -rw- weinberger
2013-03-13 20:38 ` Martitz, Thomas
2013-03-13 20:46 ` Eric W. Biederman
2013-03-13 21:07 ` AW: " Martitz, Thomas
2013-03-13 21:21 ` Eric W. Biederman
2013-03-13 22:01 ` AW: " Martitz, Thomas
2013-03-15 7:30 ` Thomas Martitz
2013-03-15 8:59 ` Eric W. Biederman
2013-03-15 13:49 ` Thomas Martitz
2013-03-15 13:56 ` richard -rw- weinberger
2013-03-15 14:08 ` Thomas Martitz
2013-03-15 14:16 ` richard -rw- weinberger
2013-03-15 14:20 ` Thomas Martitz
2013-03-15 14:32 ` richard -rw- weinberger
2013-03-15 14:35 ` Thomas Martitz [this message]
2013-03-15 14:45 ` richard -rw- weinberger
2013-03-15 14:50 ` Thomas Martitz
2013-03-15 15:07 ` Thomas Martitz
2013-03-15 15:15 ` Hannes Frederic Sowa
2013-03-15 15:37 ` Benjamin LaHaise
2013-03-15 19:48 ` Martitz, Thomas
2013-03-18 9:33 ` Thomas Martitz
2013-03-15 18:36 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2013-03-11 9:49 Thomas Martitz
2013-03-11 9:25 Thomas Martitz
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=514331BC.4080802@hhi.fraunhofer.de \
--to=thomas.martitz@hhi.fraunhofer.de \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=richard.weinberger@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.