LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lukas Razik <linux@razik.name>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ethernet over Kernel Sockets
Date: Mon, 03 Mar 2008 22:04:53 +0100	[thread overview]
Message-ID: <47CC67F5.6030505@razik.name> (raw)
In-Reply-To: <20080302104650.GC3861@ucw.cz>

Hello Pavel!

Thanks for your answer!

>>As you know, some network cards doesn't have a 'eth' 
>>interface under linux.
>>Because of that I'm developing a net_device based driver 
>>which doesn't transmit and receive directly through a 
>>real network card but through UDP kernel sockets.
> 
> What is it good for?

It's good for network cards which have a socket implementation but no 
'eth' interface which is needed by some applications...

>>The interesting thing is, that I always get PingPongs of 
>>1ms (= one jiffie). Although if I measure with 100MBit- 
>>or other non-Ethernet cards.
> 
> Try increasing HZ :-)... or maybe it is a gigabit interrupt mitigation
> issue?

Yes, that would have been a nice solution for an OS-freak (like me and 
sure like you) but there are also other people :-/ who want to run more 
than the really nice linux kernel on their machines... ;-)))

The performance brake was the kernel thread for receiving packets. My 
solution are socket callbacks.
The idea I've got from someone of the kernelnewbies mailing list and 
some other people. Now I've PingPong times of ~30µsec (with Ethernet 
over Sockets over Ethernet, which natively has ~23µsec).

For interested people:
http://mail.nl.linux.org/kernelnewbies/2008-03/msg00005.html

Regards,
Lukas

      reply	other threads:[~2008-03-03 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 20:54 Lukas Razik
2008-03-02 10:46 ` Pavel Machek
2008-03-03 21:04   ` Lukas Razik [this message]

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=47CC67F5.6030505@razik.name \
    --to=linux@razik.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --subject='Re: Ethernet over Kernel Sockets' \
    /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

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).