| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: migrating to lock_sock() |
| From: | Henner Eisen <eis@xxxxxxxxxxxxx> |
| Date: | Wed, 20 Dec 2000 00:36:33 +0100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200012191516.SAA13781@xxxxxxxxxxxxx> (kuznet@xxxxxxxxxxxxx) |
| References: | <200012191516.SAA13781@xxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
>>>>> "kuznet" == kuznet <kuznet@xxxxxxxxxxxxx> writes:
kuznet> sock_alloc_send_skb() is stateless, there is no lock to
kuznet> release.
kuznet> If your protocol uses socket lock, you cannot use this
kuznet> function.
o.k., thus I need to implement an own function. Would it make sense
to implement it inside the network core such that other protocols
that want to migrate to lock_sock() locking can re-use it?
Henner
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | lapb module irq context problems, Henner Eisen |
|---|---|
| Next by Date: | Re: alignment issues on netif_rx, Jes Sorensen |
| Previous by Thread: | Re: migrating to lock_sock(), kuznet |
| Next by Thread: | Re: migrating to lock_sock(), kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |