• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NKE.pdf
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NKE.pdf


  • Subject: Re: NKE.pdf
  • From: Joshua Graessley <email@hidden>
  • Date: Mon, 16 Jun 2003 10:47:49 -0700

On Monday, June 16, 2003, at 3:13, Stiphane Sudre wrote:

On jeudi, juin 12, 2003, at 00:05 Europe/Paris, Vincent Lubet wrote:

I should add the NKEMgr is deprecated and should not be used for new development.

How much deprecated?

The NKEMgr was never loaded by default. It is still being shipped with the system, but no work has been done on the NKEMgr for years now.

On mercredi, juin 11, 2003, at 22:50 Europe/Paris, Joshua Graessley wrote:

The PF_NKE protocol has been deprecated. It was actually implemented in an NKE manager kext. The recommended way of communicating between user space and a kext is to use a PF_SYSTEM socket with the protocol "SYSPROTO_CONTROL". See sys/kern_control.h for more inform

Could it be possible to have a clear and official statement on this? Because I just don't understand what the official recommendation is.

* In NKE.PDF, AFAIK, the tcplogger sample code is making use of PF_NKE in its userland part. And this is said to be the deprecated part. So the only available documentation is no more correct.

The NKE.PDF is ancient as is the tcplogger sample code (pre MacOS X 10.0).

* In sys/kern_control.h, the whole API is bracketed by a #ifdef __APPLE_API_UNSTABLE. And this is the suggested solution. And there is no documentation on it or sample code.

The only available documentation is, unfortunately, in the header. It is marked as unstable because all of the kernel APIs are unstable. We reserve the right to make changes to the kernel to fix bugs and add features. There is no clear division in the kernel between APIs that kext developers may use and pieces that are internal implementation details.

We will be discussing this at WWDC this year. We have plans to introduce a sustainable API. Check out session 107 - "Kernel Programming Interfaces for Extensions". These APIs will have more documentation than the current ones. At that time, the NKE.PDF will probably be retired.

-josh
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: NKE.pdf
      • From: Stéphane Sudre <email@hidden>
References: 
 >Re: NKE.pdf (From: Stéphane Sudre <email@hidden>)

  • Prev by Date: Re: Which API should I use for sockets
  • Next by Date: Re: NKE.pdf
  • Previous by thread: Re: NKE.pdf
  • Next by thread: Re: NKE.pdf
  • Index(es):
    • Date
    • Thread