I have created D13327 on reviews.freebsd.org with a patch that keeps
track of # of issued write delegations and allows nfsrv_checkgetattr()
to return without acquiring the lock when it is 0.
Hopefully kib@, jhb@ or someone who is familiar with the use
of the atomic ops in the kernel can review it.
On Fri, Dec 1, 2017 at 2:55 PM, Shawn Webb
wrote:
> On Fri, Dec 01, 2017 at 02:53:53PM -0700, Warner Losh wrote:
> > On Fri, Dec 1, 2017 at 2:49 PM, Shawn Webb
> > wrote:
> >
> > > On Wed, Nov 29, 2017 at 07:31:17PM -0700, Warner Losh wrote:
> > > > On Wed, Nov 29, 2017 at 5:54 PM, Warner Losh
On Fri, Dec 01, 2017 at 02:53:53PM -0700, Warner Losh wrote:
> On Fri, Dec 1, 2017 at 2:49 PM, Shawn Webb
> wrote:
>
> > On Wed, Nov 29, 2017 at 07:31:17PM -0700, Warner Losh wrote:
> > > On Wed, Nov 29, 2017 at 5:54 PM, Warner Losh wrote:
> > >
> > > >
> > > >
> > > > On Wed, Nov 29, 2017 at 5:
On Fri, Dec 1, 2017 at 2:49 PM, Shawn Webb
wrote:
> On Wed, Nov 29, 2017 at 07:31:17PM -0700, Warner Losh wrote:
> > On Wed, Nov 29, 2017 at 5:54 PM, Warner Losh wrote:
> >
> > >
> > >
> > > On Wed, Nov 29, 2017 at 5:43 PM, Shawn Webb <
> shawn.w...@hardenedbsd.org>
> > > wrote:
> > >
> > >> On
On Wed, Nov 29, 2017 at 07:31:17PM -0700, Warner Losh wrote:
> On Wed, Nov 29, 2017 at 5:54 PM, Warner Losh wrote:
>
> >
> >
> > On Wed, Nov 29, 2017 at 5:43 PM, Shawn Webb
> > wrote:
> >
> >> On Wed, Nov 29, 2017 at 05:42:52PM -0700, Warner Losh wrote:
> >> > On Wed, Nov 29, 2017 at 5:34 PM, Sh
Hi All,
I am running into this error when attempting to buildworld from a
checkout I made recently (git hash 76ca06b62f3bfb21f1f2e1295eb89e3c235bdda7)
--- all_subdir_stand ---
/usr/home/pete/git/freebsd/stand/i386/libi386/libi386.a(bootinfo64.o):
In function `bi_checkcpu':
/usr/home/pete/git/
On Fri, Nov 10, 2017 at 09:12:32AM +, Roger Pau Monné wrote:
> On Fri, Nov 10, 2017 at 12:33:01AM +0100, Herbert J. Skuhra wrote:
> > On Thu, 09 Nov 2017 18:55:52 +0100,
> > Roger Pau Monné wrote:
> > >
> > > Hello,
> > >
> > > Since recently it seems like the bootonly release make target do
On 30/11/2017 23:04, Mark Millard wrote:
> The messages seem to be considered non-fatal at the system
> level, although the processes are getting signal 11. It is
> not clear to me if the signal 11's are consequences, causes,
> or just happen to be associated.
The messages are produced if there i