From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] net: xen-netback: convert to hw_features
Date: Tue, 19 Apr 2011 15:30:19 +0200 [thread overview]
Message-ID: <20110419133019.GA3973@rere.qmqm.pl> (raw)
In-Reply-To: <1303219073.5997.191.camel@zakaz.uk.xensource.com>
On Tue, Apr 19, 2011 at 02:17:53PM +0100, Ian Campbell wrote:
> On Tue, 2011-04-19 at 12:56 +0100, Michał Mirosław wrote:
> > Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> Thanks for beating me to this! However the prototype for
> xenvif_fix_features is wrong (needs to take a net_device not a xenvif).
I'll resend v2 with this fix.
> I fixed it with the following, I also moved the !can_sg MTU clamping
> into a set_features hook (like we do with netfront). Am I right that
> this pattern copes with changes to SG via ethtool etc better? I think
> it's more future proof in any case.
This looks wrong. Even if SG is turned on, you might get big skbs which
are linearized. There is a difference in SG capability and SG offload
status and as I see it the capability is what you need to test for MTU.
> NB: I'm having some issues with my test hardware at the moment so this
> is reviewed by eye and compile tested only...
>
> I'm also happy for this to be folded into the original with my
> "Signed-off-/Acked-by Ian Campbell <ian.campbell@citrix.com>" if that is
> preferable.
Thanks.
Best Regards,
Michał Mirosław
next prev parent reply other threads:[~2011-04-19 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 11:56 [PATCH] net: xen-netback: convert to hw_features Michał Mirosław
2011-04-19 13:17 ` Ian Campbell
2011-04-19 13:30 ` Michał Mirosław [this message]
2011-04-19 13:39 ` Ian Campbell
2011-04-19 13:43 ` Michał Mirosław
2011-04-19 15:15 ` Ian Campbell
2011-04-19 15:25 ` Michał Mirosław
2011-04-19 13:35 ` [PATCH v2] " Michał Mirosław
2011-04-19 13:39 ` Michał Mirosław
2011-04-20 7:58 ` Ian Campbell
2011-04-20 8:31 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110419133019.GA3973@rere.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=Ian.Campbell@eu.citrix.com \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox