The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition)


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/netgraph/bluetooth/l2cap/TODO

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

    1 $Id: TODO,v 1.1 2002/11/24 19:47:06 max Exp $
    2 $FreeBSD$
    3 
    4 FIXME/TODO list
    5 
    6 0) Ping itself. Should L2CAP layer loopback data?
    7 
    8 1) Locking/SMP
    9 
   10         External code now uses ng_send_fn to inject data into Netgraph, so
   11         it should be fine as long as Netgraph is SMP safe. Just need to
   12         verify it.
   13 
   14 2) Understand and implement L2CAP QoS
   15 
   16         Will fix later. I only have CSR based hardware and it does not
   17         support QoS.
   18 
   19 3) Better functions to manage CIDs and command ident's.
   20 
   21         Resource manager is not good because it uses MTX_DEF mutexes,
   22         (i.e. could block/sleep)
   23 
   24 4) Implement group channels (multicast)
   25 
   26         Will fix later
   27 
   28 5) Add bytes/packets counters and commands to get/reset them
   29 
   30         Will fix later. What to count?
   31 
   32 6) Better way to get information about channels
   33 
   34         L2CAP can support about 65000 channels. Need define some good way
   35         to get data from kernel to user space. For example if we need to pass
   36         1K of information for every channel, then worst case is that we need
   37         to pass 65Mbytes of data from kernel to user space. Not good.
   38 
   39 7) Deal properly with "shutdown"s and hook "disconnect"s
   40 
   41         For now we destroy all channels when upstream hook is disconnected.
   42         Is there a better way to handle this?
   43 

Cache object: 6b06a6a53e7c23410a731ade0567a2b3


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.