From: ebiederm@xmission.com (Eric W. Biederman)
To: "Martitz\, Thomas" <thomas.martitz@hhi.fraunhofer.de>
Cc: richard -rw- weinberger <richard.weinberger@gmail.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: Wed, 13 Mar 2013 13:46:07 -0700 [thread overview]
Message-ID: <87r4jjav00.fsf@xmission.com> (raw)
In-Reply-To: <3D7E565A361FB844A410A5EFCDD7BA4002ECF5@MXSRV3.fe.hhi.de> (Thomas Martitz's message of "Wed, 13 Mar 2013 20:38:08 +0000")
"Martitz, Thomas" <thomas.martitz@hhi.fraunhofer.de> writes:
>>
>> ________________________________________
>> Von: richard -rw- weinberger [richard.weinberger@gmail.com]
>> Gesendet: Mittwoch, 13. März 2013 12:13
>> An: Martitz, Thomas
>> Cc: netdev@vger.kernel.org; davem@davemloft.net; edumazet@google.com; herbert@gondor.apana.org.au; ebiederm@xmission.com
>> Betreff: Re: Trying to implement secondary loopback
>>
>> >
>> > So my questions are:
>> > * Is this on purpose/expected?
>> > * Is there anyway around it so that I can have a custom loopback interface
>> > without touching lo's functionality.
>> > * Generally, what's the proper way (if any) implement a secondary loopback
>> > interface?
>>
>> The only really question that matters is, why do you need a second
>> loopback interface?
>> Why can't you use any other pseudo interface?
>>
>
> What pseudo interface do you mean? I'm not aware of alternative pseudo interfaces.
>
> I'm developing a NIC and a driver for it. Thus I'm implementing the interface. I'm trying to implement an interface that does exactly do what loopback does except that I want to extend the loopback path to PCIe. This is for testing & validation purposes.
>
> I tried to implement an interface that's doesn't advertise as
> such. But the data transfer didn't go through my code. My test app is
> a simple client/server setup in a single process that sends/receive
> data to/on 127.0.0.1.
The easy solution is to setup two network namespaces and two nics.
And transmit data from one network namespace to another, through your
nics.
Eric
next prev parent reply other threads:[~2013-03-13 20:46 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 [this message]
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
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=87r4jjav00.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=thomas.martitz@hhi.fraunhofer.de \
/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).