Re: poor network loopback performance and scalability

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: David Miller
Date: Monday, April 21, 2008 - 1:16 am

From: Ingo Molnar <mingo@elte.hu>
Date: Mon, 21 Apr 2008 10:11:03 +0200


Please read again, that isn't the suggestion being discussed.

What's being discussed is having the top of the transmit call path
getting a socket "buffer" pointer, that it can feed back into the
packet input path directly.  Loopback would return buffer pointers
from ->hard_start_xmit() instead of passing them netif_rx().  The top
of the transmit call path, upon getting a non-NULL buffer returned,
would pass it to netif_receive_skb().

We're not talking about sockets, although that is another idea (which
I'm working on a patch for, and I have a mechanism for what you refer
to as "path validation").
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: poor network loopback performance and scalability, David Miller, (Sun Apr 20, 8:38 pm)
Re: poor network loopback performance and scalability, Ingo Molnar, (Mon Apr 21, 1:11 am)
Re: poor network loopback performance and scalability, David Miller, (Mon Apr 21, 1:16 am)
Re: poor network loopback performance and scalability, David Miller, (Mon Apr 21, 3:22 am)