netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Flavio Leitner <fbl@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: RFC limit sk_mem_quantum to 8192
Date: Tue, 21 May 2013 22:58:58 -0300	[thread overview]
Message-ID: <20130522015858.GB17240@obelix.rh> (raw)
In-Reply-To: <1369184962.3301.264.camel@edumazet-glaptop>

On Tue, May 21, 2013 at 06:09:22PM -0700, Eric Dumazet wrote:
> On Tue, 2013-05-21 at 21:45 -0300, Flavio Leitner wrote:
> > diff --git a/include/net/sock.h b/include/net/sock.h
> > index 5d84de4..d52fa2d 100644
> > --- a/include/net/sock.h
> > +++ b/include/net/sock.h
> > @@ -954,7 +954,12 @@ static inline struct inode *SOCK_INODE(struct socket *socket)
> >  extern int __sk_mem_schedule(struct sock *sk, int size, int kind);
> >  extern void __sk_mem_reclaim(struct sock *sk);
> >  
> > +#if PAGE_SIZE < 8192
> >  #define SK_MEM_QUANTUM ((int)PAGE_SIZE)
> > +#else
> > +#define SK_MEM_QUANTUM ((int)8192)
> > +#endif
> > +
> >  #define SK_MEM_QUANTUM_SHIFT ilog2(SK_MEM_QUANTUM)
> >  #define SK_MEM_SEND	0
> >  #define SK_MEM_RECV	1
> > 
> 
> What particular problem do you want to solve ?

So far there is no other problem besides the weird tcp_wmem.

> Wouldn't be easier to chose 4096 on all arches ?

Not sure what you're referring to. That config comes from a
distro kernel, so it's not under my control. If it is about
the upper limit for sk_mem_quantum, 4k seems enough to me as well.
 
> Are you sure a network driver doesn't provide skb using a full page ?

You lost me. You're saying that today we consider a page size
a minimum and so if we reduce that, the skb wouldn't fit in the
min sk memory?

Thanks,
-- 
fbl

  reply	other threads:[~2013-05-22  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  0:45 RFC limit sk_mem_quantum to 8192 Flavio Leitner
2013-05-22  1:09 ` Eric Dumazet
2013-05-22  1:58   ` Flavio Leitner [this message]
2013-05-22  2:21     ` Eric Dumazet
2013-05-22 14:31       ` Flavio Leitner

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=20130522015858.GB17240@obelix.rh \
    --to=fbl@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.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).