__KFREE_SKB(9) Linux Networking __KFREE_SKB(9)NAME
__kfree_skb - private function
SYNOPSIS
void __kfree_skb(struct sk_buff * skb);
ARGUMENTS
skb
buffer
DESCRIPTION
Free an sk_buff. Release anything attached to the buffer. Clean the state. This is an internal helper function. Users should always call
kfree_skb
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 __KFREE_SKB(9)
Check Out this Related Man Page
WIMAX_MSG_ALLOC(9) Linux Networking WIMAX_MSG_ALLOC(9)NAME
wimax_msg_alloc - Create a new skb for sending a message to userspace
SYNOPSIS
struct sk_buff * wimax_msg_alloc(struct wimax_dev * wimax_dev, const char * pipe_name, const void * msg, size_t size, gfp_t gfp_flags);
ARGUMENTS
wimax_dev
WiMAX device descriptor
pipe_name
"named pipe" the message will be sent to
msg
pointer to the message data to send
size
size of the message to send (in bytes), including the header.
gfp_flags
flags for memory allocation.
RETURNS
0 if ok, negative errno code on error
DESCRIPTION
Allocates an skb that will contain the message to send to user space over the messaging pipe and initializes it, copying the payload.
Once this call is done, you can deliver it with wimax_msg_send.
IMPORTANT
Don't use skb_push/skb_pull/skb_reserve on the skb, as wimax_msg_send depends on skb->data being placed at the beginning of the user
message.
Unlike other WiMAX stack calls, this call can be used way early, even before wimax_dev_add is called, as long as the wimax_dev->net_dev
pointer is set to point to a proper net_dev. This is so that drivers can use it early in case they need to send stuff around or communicate
with user space.
COPYRIGHT Kernel Hackers Manual 2.6. July 2010 WIMAX_MSG_ALLOC(9)
Hi,
I found on linuxgazette.net/93/bhaskaran.html page very useful sample of virtual driver (not connected to real hardware).
I try to compile it with no effect.
So:
I got fresh Ubuntu 9.10 (kernel 2.6.31-14)
My source is saved in networkAdapter.c file in /usr/src/myModules directory.
I... (21 Replies)
I am having trouble resuming from hibernation using TuxOnIce method.
The thing works, but in a very strange manner. Here's how it looks:
1. Computer boots and finds resume image and starts resume. It reads image from disk (takes ~10 seconds)
Reading kernel & process data...
Atomic restore.... (8 Replies)