[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e108260812160800h66e525f2p8c6c78b1b73630d1@mail.gmail.com>
Date: Tue, 16 Dec 2008 17:00:07 +0100
From: "Bart Van Assche" <bart.vanassche@...il.com>
To: "Evgeniy Polyakov" <zbr@...emap.net>
Cc: "Vladislav Bolkhovitin" <vst@...b.net>, linux-scsi@...r.kernel.org,
"James Bottomley" <James.Bottomley@...senpartnership.com>,
linux-kernel@...r.kernel.org, scst-devel@...ts.sourceforge.net,
netdev@...r.kernel.org
Subject: Re: [PATCH][RFC 23/23]: Support for zero-copy TCP transmit of user space data
On Wed, Dec 10, 2008 at 10:45 PM, Evgeniy Polyakov <zbr@...emap.net> wrote:
> Another approach is to increase skb's shared data (at the end of the
> skb->data), and this approach was not frowned upon too much either, but
> it requires to mess with skb->destructor, which may not be appropriate
> in some cases. If iscsi does not use sockets (it does iirc), things are
> much simpler.
Hello Evgeniy,
Any idea whether it would be acceptable to extend "struct sock" with
one or two pointers to callback functions ? These callback functions
could be called from skb_release_data() etc. through the "struct sock*
sk" member of "struct sk_buff".
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists