From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH] net, gro: fix the truesize of all fragments
Date: Fri, 20 Dec 2013 18:21:10 +0400 [thread overview]
Message-ID: <52B45256.3010602@cogentembedded.com> (raw)
In-Reply-To: <CAEH94LhiQGG-_Ad-5KYKt20CBYkQ6YR+s93zPeELzR-fGZ4yTA@mail.gmail.com>
Hello.
On 20-12-2013 17:59, Zhi Yong Wu wrote:
>>> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>>> When the truesize of all fragments was calculated, it didn't take
>>> the first small piece of data into account.
>>> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>>> ---
>>> net/core/skbuff.c | 10 +++++++---
>>> 1 files changed, 7 insertions(+), 3 deletions(-)
>>> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
>>> index 2b6b863..0665bd6 100644
>>> --- a/net/core/skbuff.c
>>> +++ b/net/core/skbuff.c
>>> @@ -3027,9 +3027,12 @@ int skb_gro_receive(struct sk_buff **head, struct
>>> sk_buff *skb)
>>> frag->page_offset += offset;
>>> skb_frag_size_sub(frag, offset);
>>>
>>> - /* all fragments truesize : remove (head size + sk_buff)
>>> */
>>> + /**
>> Why kernel-doc style comment here? Networking code uses the following
>> comment style:
>> /* bla
>> * bla
>> */
> No, If you check other comments in networking code,
I suggest you do this, and not only comments before functions but also
inside them. I also suggest that you read chapter 8 of Documentation/CodingStyle.
> you will see why i
> did as that.
I repeat, this is kernel-doc style comment, that is used to comment on a
functions/structures, and then can be automatically processed to create kernel
documentation. Your case does not fit for /** comment.
> /**
> * skb_segment - Perform protocol segmentation on skb.
> * @skb: buffer to segment
> * @features: features for the output path (see dev->features)
> *
> * This function performs segmentation on the given skb. It returns
> * a pointer to the first in a list of new skbs for the segments.
> * In case of error it returns ERR_PTR(err).
> */
> struct sk_buff *skb_segment
>>> + * all fragments truesize :
>>> + * remove (head size + sk_buff + offset)
>>> + */
>>> delta_truesize = skb->truesize -
>>> - SKB_TRUESIZE(skb_end_offset(skb));
>>> + SKB_TRUESIZE(skb_end_offset(skb) +
>>> offset);
>>>
>>> skb->truesize -= skb->data_len;
>>> skb->len -= skb->data_len;
>>
>>
>> WBR, Sergei
> Sorry, what is WBR?
With best regards. Nothing offensive. :-)
WBR, Sergei
next prev parent reply other threads:[~2013-12-20 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 11:45 [RFC PATCH] net, gro: fix the truesize of all fragments Zhi Yong Wu
2013-12-20 13:52 ` Sergei Shtylyov
2013-12-20 13:59 ` Zhi Yong Wu
2013-12-20 14:21 ` Sergei Shtylyov [this message]
2013-12-20 14:34 ` Zhi Yong Wu
2013-12-20 14:28 ` Eric Dumazet
2013-12-20 14:37 ` Zhi Yong Wu
2013-12-20 14:42 ` Eric Dumazet
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=52B45256.3010602@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).