Re: Last call: removing the INT_MAX limit on max i/o size

From: Alfred Perlstein <alfred_at_freebsd.org>
Date: Fri, 17 Feb 2012 23:46:56 -0800
* Konstantin Belousov <kostikbel_at_gmail.com> [120217 17:54] wrote:
> This is a notification to allow you to comment on the patch before the
> commit.
> 
> I will commit the latest version of the patch to remove the limitation
> of the maximal i/o size for read/write syscalls to INT_MAX in the
> beginning of the next week.
> 
> The change is available at
> http://people.freebsd.org/~kib/misc/uio_resid.10.patch
> various versions of it were discussed with Bruce Evance and David Schultz.
> 
> Patch does not enable SSIZE_MAX-sized i/o by default, hiding this under
> debug.iosize_max_clamp sysctl. Effectively, the patch becomes the pass
> to change various ints into ssize_t.

I always wonder if it's worth defining a type for this, resid_t or
something, therefor you could use some tricks to generate warnings
when it's cast to a type that normally would not generate warnings
but could cause some loss or issue otherwise.

Probably not.

-- 
- Alfred Perlstein
.- VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10
.- FreeBSD committer
Received on Sat Feb 18 2012 - 07:02:09 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:24 UTC