mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [RFD] Pluggable code design (was: can we reuse an skb)
       [not found]   ` <1f808b4a0906202241l1d74364ft52d99ecb6b0274f5@mail.gmail.com>
@ 2009-06-21 11:46     ` Al Boldi
  0 siblings, 0 replies; only message in thread
From: Al Boldi @ 2009-06-21 11:46 UTC (permalink / raw)
  To: Peter Chacko, David Miller
  Cc: rick.jones2, radhamohan_ch, netdev, linux-kernel

Peter Chacko wrote:
> What i am considering here is the super optimization of memory buffers
> for a multi-layer packet processor, without needing to move packets
> into user space. In that case, i am optimizing my custom network stack
> with a pre-allocated MTU sized and a few  jumbo-sized buffers. And no
> interrupts as i do NAPI at all times, as this is a dedicated
> appliance. I keep all these buffers in the L1 cache and hence i have
> different sets of pools for different cores. I  am currently guiding
> my engineers to implement the code changes now..

Yes, having a customizable/pluggable network stack sounds very useful.

In general, OpenSource projects like Linux don't give much incentive to 
pluggable designs, because the source, being open, represents a weired form 
of pluggability.  Unfortunately, this "hack it up / code it hard" design 
style usually inhibits healthy development.

A rethink is probably in place...


Thanks!

--
Al

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-21 11:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <962874.62146.qm@web94813.mail.in2.yahoo.com>
     [not found] ` <20090619.162957.156347025.davem@davemloft.net>
     [not found]   ` <1f808b4a0906202241l1d74364ft52d99ecb6b0274f5@mail.gmail.com>
2009-06-21 11:46     ` [RFD] Pluggable code design (was: can we reuse an skb) Al Boldi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®