• 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
TCP socket filter and control/flags params to sf_data functions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TCP socket filter and control/flags params to sf_data functions


  • Subject: TCP socket filter and control/flags params to sf_data functions
  • From: jakub <email@hidden>
  • Date: Fri, 13 Nov 2009 15:10:21 +0100

Hi list,

I have read Network Kernel Extensions Programming Guide along with
TCPlognke sample code and I have one, hopefully simple question.

If I have a socket filter running on TCP protocol only (IPv4/IPv6),
do I have to bother with mbuf_t control and sflt_data_flags_t flags
parameters to sf_data_in_func/sf_data_out_func? Documentation to
sf_data_in_func also says, that in the data buffer, control data may
appear in the mbuf chain. Is this relevant for TCP?

I want to pass only data to user space process (possibly modifying the
data) and I don't want to keep a copy in kernel just to keep the flags
and control mbuf.

I haven't found any documentation discussing this in any more detail and
I'm not aware of any such control/flags used on top of TCP. Can I just
ignore these two and set them to 0 when re-injecting data? TCPlognke is
dealing with them.

Thanks a lot,

Jakub

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: cross-process timeoutable semaphores
  • Next by Date: Open Source Releases
  • Previous by thread: fdatasync()
  • Next by thread: Open Source Releases
  • Index(es):
    • Date
    • Thread