From: David Miller <davem@davemloft.net>
To: dmitry@broadcom.com
Cc: netdev@vger.kernel.org, vladz@broadcom.com, eilong@broadcom.com
Subject: Re: [PATCH net-next 2/5] bnx2x: save cycles in setting gso_size
Date: Sun, 10 Oct 2010 20:52:54 -0700 (PDT) [thread overview]
Message-ID: <20101010.205254.193716921.davem@davemloft.net> (raw)
In-Reply-To: <1286749675.4669.24.camel@lb-tlvb-dmitry>
From: "Dmitry Kravkov" <dmitry@broadcom.com>
Date: Mon, 11 Oct 2010 00:27:55 +0200
> diff --git a/drivers/net/bnx2x/bnx2x_cmn.c b/drivers/net/bnx2x/bnx2x_cmn.c
> index cb2a3d6..ddf90e1 100644
> --- a/drivers/net/bnx2x/bnx2x_cmn.c
> +++ b/drivers/net/bnx2x/bnx2x_cmn.c
> @@ -277,8 +277,7 @@ static int bnx2x_fill_frag_skb(struct bnx2x *bp, struct bnx2x_fastpath *fp,
>
> /* This is needed in order to enable forwarding support */
> if (frag_size)
> - skb_shinfo(skb)->gso_size = min((u32)SGE_PAGE_SIZE,
> - max(frag_size, (u32)len_on_bd));
> + skb_shinfo(skb)->gso_size = 1;
>
I wonder why you need to set this here.
When you pass this packet into the stack, dev_gro_receive() is going
to set ->gro_size() unconditionally if any GRO processing is going to
occur at all.
Why do you need to set it at all?
And if we do need it, doesn't every driver that builds fragmented SKBs?
And if it's correct, why is setting a don't care value like "1" ok and
will not cause problems to whoever cares about this value?
I really want all of these questions answered, and at least lightly
explained in the commit message before I apply this patch.
Thanks.
next prev parent reply other threads:[~2010-10-11 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 22:27 [PATCH net-next 2/5] bnx2x: save cycles in setting gso_size Dmitry Kravkov
2010-10-11 3:52 ` David Miller [this message]
2010-10-11 8:53 ` Vladislav Zolotarov
2010-10-11 14:00 ` Ben Hutchings
2010-10-11 17:06 ` Vladislav Zolotarov
2010-10-11 17:48 ` 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=20101010.205254.193716921.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.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