| To: | andrew may <acmay@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: I need sk_buff frag_list info. |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Sat, 16 Mar 2002 01:54:34 +0100 |
| Cc: | Andi Kleen <ak@xxxxxxx>, Mark Wisner <markwiz@xxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20020315164721.A1097@xxxxxxxxxxxxxxx> |
| References: | <OF1B1A2F76.97320533-ON85256B7D.00695592@xxxxxxxxxxxxxxx> <20020316013712.A10179@xxxxxxxxxxxxx> <20020315164721.A1097@xxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
On Fri, Mar 15, 2002 at 04:47:21PM -0800, andrew may wrote: > So if you suggest to use ->frags should the skb->data be left alone? > I can see no way off knowing ahead of time wether the ptr's giving to > hardware for a rx will be used for the start of a packet. The headers should be in skb->data if possible. If not the stack will do some copying. So you could put some arbitary first fragment (e.g. 128 bytes) there. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: I need sk_buff frag_list info., andrew may |
|---|---|
| Next by Date: | kernel support for l2tp, Arthur Scherbius |
| Previous by Thread: | Re: I need sk_buff frag_list info., andrew may |
| Next by Thread: | Re: I need sk_buff frag_list info., Donald Becker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |