[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1343689678.2667.63.camel@bwh-desktop.uk.solarflarecom.com>
Date: Tue, 31 Jul 2012 00:07:58 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Stephen Hemminger <shemminger@...tta.com>
CC: David Miller <davem@...emloft.net>, <eric.dumazet@...il.com>,
<netdev@...r.kernel.org>, <linux-net-drivers@...arflare.com>
Subject: Re: [PATCH net 1/2] tcp: Limit number of segments generated by GSO
per skb
On Mon, 2012-07-30 at 15:50 -0700, Stephen Hemminger wrote:
> On Mon, 30 Jul 2012 23:20:57 +0100
> Ben Hutchings <bhutchings@...arflare.com> wrote:
>
> > On Mon, 2012-07-30 at 14:46 -0700, David Miller wrote:
> > > From: Ben Hutchings <bhutchings@...arflare.com>
> > > Date: Mon, 30 Jul 2012 20:35:52 +0100
> > >
> > > > On Mon, 2012-07-30 at 19:31 +0200, Eric Dumazet wrote:
> > > >> Or you could introduce a new wk->sk_gso_max_segments, that your sfc
> > > >> driver sets to whatever limit ?
> > > >
> > > > Yes, that's another option.
> > >
> > > This is how I want this handled.
> >
> > How should that be applied in the GRO-forwarding case?
> >
> > Ben.
> >
> Why not make max_frags a property of the device?
[...]
This has nothing to do with the number of input fragments. But I think
you're on the right track - this can be checked in netif_skb_features()
or something like that.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists