Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD

From: Evgeniy Polyakov <[email protected]>
Date: Wed, 9 Aug 2006 09:46:48 +0400

> There is another approach for that - do not use slab allocator for
> network dataflow at all. It automatically has all you pros amd if
> implemented correctly can have a lot of additional usefull and
> high-performance features like full zero-copy and total fragmentation
> avoidance.

Free advertisement for your network tree allocator Evgeniy? :-)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
    • From: Evgeniy Polyakov <[email protected]>

• References:
  • [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
    • From: Peter Zijlstra <[email protected]>
  • Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
    • From: Evgeniy Polyakov <[email protected]>

• Prev by Date: Re: 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager!
• Next by Date: [BUG?] possible recursive locking detected (blkdev_open)
• Previous by thread: Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
• Next by thread: Re: [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]