| To: | "Chad N. Tindel" <chad@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Wrong UIDs reported in /proc/net/tcp |
| From: | David Stevens <dlstevens@xxxxxxxxxx> |
| Date: | Thu, 18 Nov 2004 15:56:43 -0800 |
| Cc: | linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx, Stephen Hemminger <shemminger@xxxxxxxx> |
| In-reply-to: | <20041118234911.GA66056@calma.pair.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Wrong UIDs reported in /proc/net/tcp, Chad N. Tindel |
|---|---|
| Next by Date: | [PATCH] 5/5: eepro: fix auto-detection option, Aristeu Sergio Rozanski Filho |
| Previous by Thread: | Re: Wrong UIDs reported in /proc/net/tcp, Chad N. Tindel |
| Next by Thread: | Re: Wrong UIDs reported in /proc/net/tcp, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |