On Thu, 2012-01-05 at 19:15 +0000, David Miller wrote:
> From: Ian Campbell <ian.campbell@xxxxxxxxxx>
> Date: Thu, 5 Jan 2012 17:13:43 +0000
>
> > -static ssize_t do_tcp_sendpages(struct sock *sk, struct page **pages, int poffset,
> > +static ssize_t do_tcp_sendpages(struct sock *sk,
> > + struct page **pages,
> > + struct skb_frag_destructor **destructors,
> > + int poffset,
> > size_t psize, int flags)
> > {
> > struct tcp_sock *tp = tcp_sk(sk);
>
> An array of destructors is madness, and the one call site that specifies this
> passes an address of a single entry.
I figured it was easy enough to accommodate the multiple destructor case
but you are right that is overkill given the current (and realistically,
expected) usage, I'll change that for the next round.
(that's assuming we don't end up with some scheme where the struct page
* is in the destructor struct like I was investigating previously to
alleviate the frag size overhead. I guess this illustrates nicely why
that approach got ugly: these array propagate all the way up the call
chain if you do that)
> This also would never even have to occur if you put the destructor inside of
> struct page instead.
>
> Finally, except for the skb_shared_info() layout optimization in patch #1 which
> I alreayd applied, this stuff is not baked enough for the 3.3 merge window.
Sure thing, I should have made it clear in my intro mail that I was
aiming for 3.4.
Thanks,
Ian
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
