From: Alexander Duyck <alexander.h.duyck@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ixgbe: normalize frag_list usage
Date: Thu, 07 Oct 2010 12:59:14 -0700 [thread overview]
Message-ID: <4CAE2692.8020401@intel.com> (raw)
In-Reply-To: <20101006.235837.241424681.davem@davemloft.net>
On 10/6/2010 11:58 PM, David Miller wrote:
> From: "Duyck, Alexander H"<alexander.h.duyck@intel.com>
> Date: Tue, 5 Oct 2010 15:45:32 -0700
>
>> The patch below is kind of what I had in mind for a way to do RSC and maintain
>> the pointer scheme you are looking for. Consider this patch an RFC for now
>> since I based this off of Jeff's internal testing tree and so it would need
>> some modification to apply cleanly to net-next.
>
> Can you really not remember the head somewhere?
I can track it in the RSC_CB if that works for you. Right now though I
guess I am not seeing the difference between tracking this in
skb->frag_next vs IXGBE_RSC_CB(skb)->frag_head. I think it might help
if you were to provide some functions that demonstrate exactly what you
had in mind for frag list handling. Specifically if you were to add a
function for merging a frag into the frag list, and for how you want to
approach cleaning up the skb->prev/frag_tail_tracker pointer when you
are cleaning up an active frag_list.
> What I wanted is for everyone to build their frag list SKBs from head to tail,
> always. So that I could, as I mentioned in my original posting, do something
> like:
My change is doing just that. It is building from head to tail. The
only difference is that tail is tracking head since it has to be updated
after the tail is added, and then I can drop next/frag_next back to NULL.
> struct sk_buff {
> union {
> struct list_head list;
> struct {
> struct sk_buff *frag_next;
> struct sk_buff *frag_tail_tracker;
> };
> };
> };
>
> The ->frag_tail_tracker is only used in the head SKB to maintain where the
> last SKB in the frag list is.
That is what I was doing in the head skb.
> You're tracking the head from the inner SKBs, such that my intended
> conventions are not being followed.
What I am doing is tracking the head from the tail skb. The reason for
this is that I need some way to update the len, data_len, and truesize
after I have placed data in the tail via skb_put. All of the other SKBs
in the frag list are just tracking the next like any other SKB in the
frag_list.
Now that I think about it I guess the issue is that I am adding the SKB
to the frag_list before it is complete. I will send another patch out
in the next couple of hours that should address most of the issues.
Thanks,
Alex
next prev parent reply other threads:[~2010-10-07 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 6:54 ixgbe: normalize frag_list usage David Miller
2010-10-04 15:37 ` Rose, Gregory V
2010-10-04 18:04 ` Alexander Duyck
2010-10-04 18:32 ` David Miller
2010-10-04 19:49 ` Alexander Duyck
2010-10-05 22:45 ` Duyck, Alexander H
2010-10-06 3:08 ` David Miller
2010-10-07 6:58 ` David Miller
2010-10-07 19:59 ` Alexander Duyck [this message]
2010-10-14 2:17 ` David Miller
2010-10-08 23:57 ` [RFC] ixgbe: v3 " Duyck, Alexander H
2010-10-25 19:47 ` 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=4CAE2692.8020401@intel.com \
--to=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
/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).