All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Stevens <dlstevens@us.ibm.com>
To: "Chad N. Tindel" <chad@tindel.net>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com,
	netdev-bounce@oss.sgi.com,
	Stephen Hemminger <shemminger@osdl.org>
Subject: Re: Wrong UIDs reported in /proc/net/tcp
Date: Thu, 18 Nov 2004 15:56:43 -0800	[thread overview]
Message-ID: <OFC99BB8DD.C1F76875-ON88256F50.0082ECFE-88256F50.00838992@us.ibm.com> (raw)
In-Reply-To: <20041118234911.GA66056@calma.pair.com>

Hmm, well, for fixed-length records, at least you could make the buffer

(pagesize/recordsize) * recordsize and avoid getting partial records,
though you could still miss some or get duplicates. At least they would
be complete records rather than a mix of unrelated ones.

Might be more intuitive semantics if the first read resulted in a complete
copy of the data at that point, fed back to the application in whatever
chunks it wants, but only if the buffering didn't eat lots of memory.

                                        +-DLS

  reply	other threads:[~2004-11-18 23:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 20:53 Wrong UIDs reported in /proc/net/tcp Chad N. Tindel
2004-11-09 21:06 ` Herbert Xu
2004-11-09 22:43   ` Chad N. Tindel
2004-11-09 22:58     ` Herbert Xu
2004-11-09 23:04       ` Chad N. Tindel
2004-11-09 23:18         ` Herbert Xu
2004-11-18 19:02   ` Chad N. Tindel
2004-11-18 21:03     ` Herbert Xu
2004-11-18 21:27       ` Stephen Hemminger
2004-11-18 22:07         ` Herbert Xu
2004-11-18 22:16           ` David Stevens
2004-11-18 23:40             ` Herbert Xu
2004-11-18 23:49             ` Chad N. Tindel
2004-11-18 23:56               ` David Stevens [this message]
2004-11-19  1:26                 ` Herbert Xu
2004-11-19 21:01       ` Chad N. Tindel
2004-11-19 14:27     ` Henrik Nordstrom
2004-11-09 21:11 ` akepner
2004-11-09 22:41   ` Chad N. Tindel

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=OFC99BB8DD.C1F76875-ON88256F50.0082ECFE-88256F50.00838992@us.ibm.com \
    --to=dlstevens@us.ibm.com \
    --cc=chad@tindel.net \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev-bounce@oss.sgi.com \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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.