Date: Sun, 20 Jul 2014 11:56:38 -0400 (EDT) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: jhb@freebsd.org Cc: net@freebsd.org Subject: Re: NFS client READ performance on -current Message-ID: <201407201556.s6KFuchL013781@hergotha.csail.mit.edu> In-Reply-To: <201407151034.54681.jhb@freebsd.org> References: <2136988575.13956627.1405199640153.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <201407151034.54681.jhb@freebsd.org>, jhb@freebsd.org writes: >Hmm, I am surprised by the m_pullup() behavior that it doesn't just >notice that the first mbuf with a cluster has the desired data already >and returns without doing anything. The specification of m_pullup() is that it returns a *writable* mbuf (and thus also that the "length" provided is less than MHLEN). Clusters are read-only. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201407201556.s6KFuchL013781>