I think "struct socket" is a socket which operates a transport layer.
It allows the flexibility to add your own protocol stack (where you can
defined your own protocol specific handlers like bind, connect, send,
revc etc..). "struct sock" is operating at network layer. It holds all
the connec
can anyone tell me the differences between "struct sock" and "struct socket"
that are data structures of network protocol stack ?
Get your new Email address!
Grab the Email name you've always wanted before someone else does!
http://mail.promotions.yahoo.com/newdomains/aa/
Hi All,
I am interested implementing some core networking projects ( such
as Network stack optimization (such as FreeBSD netperf , IPv6 etc ) .
kindly guide me on this.
regards,
Onkar
So, having kernel code which does:
set_current_state(TASK_INTERRUPTIBLE);
schedule();
causes blocking, as expected, and /proc/stat shows increasing idle
task time and non increasing io wait time. Fine.
Changing schedule() to io_schedule(), time now seems to be split
between idle task and io_wait
Hello,
I am working on a kernel module and need read/write locks of the bh-kind
due to the module needing to process input from a proc-variable. To
avoid deadlocks, I need to use trylock to determine if somebody is
holding the lock or not. Unfortunately, I cannot find a trylock_bh for
the rea
On Sat, Mar 28, 2009 at 2:27 PM, Sandeep K Sinha
wrote:
> On Sat, Mar 28, 2009 at 3:18 AM, Greg Freemyer
> wrote:
>> Sandeep,
>>
>> I've looked at the code and made comments. I suspect the issue is an
>> extraneous call
>>
>> dst_bhptr = sb_bread(ohsm_sb, dest_bh.b_blocknr);
>>
>> If that
