Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750758AbWEDRQL (ORCPT ); Thu, 4 May 2006 13:16:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750760AbWEDRQL (ORCPT ); Thu, 4 May 2006 13:16:11 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:54492 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1750758AbWEDRQL (ORCPT ); Thu, 4 May 2006 13:16:11 -0400 Subject: Re: limits / PIPE_BUF? From: Arjan van de Ven To: Vadim Lobanov Cc: linux-kernel@vger.kernel.org In-Reply-To: References: <1146725882.3101.11.camel@laptopd505.fenrus.org> Content-Type: text/plain Date: Thu, 04 May 2006 19:16:08 +0200 Message-Id: <1146762968.3101.65.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 565 Lines: 16 On Thu, 2006-05-04 at 09:39 -0700, Vadim Lobanov wrote: > How does the kernel > code ensure that this value is honored, considering that PIPE_BUF is > not > referenced in any of the pipe code? the kernel implementation guarantees one page basically, and on all architectures that I know of that's at least 4096 bytes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/