All of lore.kernel.org
 help / color / mirror / Atom feed
From: mindentropy@gmail.com (mindentropy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Regarding connector netlink running out of buffer space.
Date: Sat, 30 Jul 2011 02:05:00 +0530	[thread overview]
Message-ID: <201107300205.00964.mindentropy@gmail.com> (raw)

Hi,
  I am trying to benchmark connector netlink and am passing a file and sending 
the same to listening userspace app's using connectors i.e. cat filename > 
/dev/myconnector and an app listening. When I do this I always run into 
ENOBUFS or "No buffer space available" for files greater than 2MB. 
Now how should I fix this? 
a) Increase the socket buffers? My rmem_max is 131071 and rmem_default is 
126976
b) Should I check for the seq and ack and resend the packets? If yes how much 
packets should I not discard to do a resend?

Are there any other ways? Also I am not sure why local loop would cause 
enobufs? I am running this on a quad core with 3G of RAM.

Thanks.

             reply	other threads:[~2011-07-29 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 20:35 mindentropy [this message]
2011-07-29 20:53 ` Regarding connector netlink running out of buffer space Jeff Haran
2011-07-29 21:02   ` mindentropy

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=201107300205.00964.mindentropy@gmail.com \
    --to=mindentropy@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.