diff options
| author | Julian Elischer <julian@FreeBSD.org> | 2004-06-26 22:24:16 +0000 |
|---|---|---|
| committer | Julian Elischer <julian@FreeBSD.org> | 2004-06-26 22:24:16 +0000 |
| commit | 3ca24c284d7116d2764cd8bca4fa357a0bea07db (patch) | |
| tree | 5db990cf15727892f404908f26b492b9f1b8a509 /sys/netgraph/ng_sample.c | |
| parent | 802fc49d8afb5b8d73ae8a299d7c307693ba7555 (diff) | |
Notes
Diffstat (limited to 'sys/netgraph/ng_sample.c')
| -rw-r--r-- | sys/netgraph/ng_sample.c | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/sys/netgraph/ng_sample.c b/sys/netgraph/ng_sample.c index 20a30560d0e5..48b58c7c51a9 100644 --- a/sys/netgraph/ng_sample.c +++ b/sys/netgraph/ng_sample.c @@ -310,12 +310,12 @@ ng_xxx_rcvmsg(node_p node, item_p item, hook_p lasthook) /* * Receive data, and do something with it. * Actually we receive a queue item which holds the data. - * If we free the item it wil also froo the data and metadata unless - * we have previously disassociated them using the NGI_GET_xxx() macros. + * If we free the item it will also free the data unless we have + * previously disassociated it using the NGI_GET_M() macro. * Possibly send it out on another link after processing. * Possibly do something different if it comes from different - * hooks. the caller will never free m or meta, so - * if we use up this data or abort we must free BOTH of these. + * hooks. The caller will never free m, so if we use up this data or + * abort we must free it. * * If we want, we may decide to force this data to be queued and reprocessed * at the netgraph NETISR time. @@ -358,15 +358,15 @@ ng_xxx_rcvdata(hook_p hook, item_p item ) return (ENETUNREACH); } /* If we were called at splnet, use the following: - * NG_SEND_DATA(error, otherhook, m, meta); if this + * NG_SEND_DATA_ONLY(error, otherhook, m); if this * node is running at some SPL other than SPLNET * then you should use instead: error = - * ng_queueit(otherhook, m, meta); m = NULL: meta = - * NULL; this queues the data using the standard - * NETISR system and schedules the data to be picked + * ng_queueit(otherhook, m, NULL); m = NULL; + * This queues the data using the standard NETISR + * system and schedules the data to be picked * up again once the system has moved to SPLNET and - * the processing of the data can continue. after - * these are run 'm' and 'meta' should be considered + * the processing of the data can continue. After + * these are run 'm' should be considered * as invalid and NG_SEND_DATA actually zaps them. */ NG_FWD_NEW_DATA(error, item, xxxp->channel[chan].hook, m); |
