From: Eric Dumazet <eric.dumazet@gmail.com>
To: Matthew Wilcox <willy@infradead.org>, davem@davemloft.net
Cc: hch@lst.de, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] Beginnings of skb_frag -> bio_vec conversion
Date: Wed, 1 May 2019 04:14:41 -0400 [thread overview]
Message-ID: <639880c6-5703-857c-8a70-82fbb5a90238@gmail.com> (raw)
In-Reply-To: <20190501041757.8647-1-willy@infradead.org>
On 4/30/19 9:17 PM, Matthew Wilcox wrote:
> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>
> It turns out there's a lot of accessors for the skb_frag, which would
> make this conversion really easy if some drivers didn't bypass them.
> This is what I've done so far; my laptop's not really beefy enough to
> cope with changing skbuff.h too often ;-)
>
> This would be a great time to tell me I'm going about this all wrong.
> I already found one problem in this patch set; some of the drivers should
> have been converted to skb_frag_dma_map() instead of fixing the arguments
> to dma_map_page(). But anyway, I need sleep.
>
I guess the missing part here is the "why" all this is done ?
32 bit hosts will have bigger skb_shared_info and this impacts sk_rcvbuf and sk_sndbuf limits.
17 * 4 are 68 extra bytes per skb.
next prev parent reply other threads:[~2019-05-01 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 4:17 [PATCH 0/5] Beginnings of skb_frag -> bio_vec conversion Matthew Wilcox
2019-05-01 4:17 ` [PATCH 1/5] net: Increase the size of skb_frag_t Matthew Wilcox
2019-05-01 4:17 ` [PATCH 2/5] net: Reorder the contents " Matthew Wilcox
2019-05-01 4:17 ` [PATCH 3/5] net: Include bvec.h in skbuff.h Matthew Wilcox
2019-05-01 4:17 ` [PATCH 4/5] net: Use skb accessors for skb->page Matthew Wilcox
2019-05-02 10:21 ` kbuild test robot
2019-05-01 4:17 ` [PATCH 5/5] net: Rename skb_frag page to bv_page Matthew Wilcox
2019-05-01 8:14 ` Eric Dumazet [this message]
2019-05-01 9:44 ` [PATCH 0/5] Beginnings of skb_frag -> bio_vec conversion Matthew Wilcox
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=639880c6-5703-857c-8a70-82fbb5a90238@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=netdev@vger.kernel.org \
--cc=willy@infradead.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