From owner-freebsd-arch@FreeBSD.ORG  Sat Feb 18 08:02:09 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 650E21065673;
	Sat, 18 Feb 2012 08:02:09 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 556238FC12;
	Sat, 18 Feb 2012 08:02:09 +0000 (UTC)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 3C5361A3C4D; Fri, 17 Feb 2012 23:46:56 -0800 (PST)
Date: Fri, 17 Feb 2012 23:46:56 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: Konstantin Belousov <kostikbel@gmail.com>
Message-ID: <20120218074655.GF31998@elvis.mu.org>
References: <20120218015428.GC3283@deviant.kiev.zoral.com.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120218015428.GC3283@deviant.kiev.zoral.com.ua>
User-Agent: Mutt/1.4.2.3i
Cc: arch@freebsd.org, current@freebsd.org
Subject: Re: Last call: removing the INT_MAX limit on max i/o size
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2012 08:02:09 -0000

* Konstantin Belousov <kostikbel@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