Hi,
I would like to know why quota is not enabled in the stock kernel..
I remembered that it is not enabled since freebsd 3.5 or freebsd 4 generation.
Now in freebsd 9.0, it still neeed a kernel rebuild.
I have heard it has performance issue (GIANT lock) about quota.
Regards,
Patrick
--- On
On Tue, Dec 25, 2012 at 09:34:30PM +0800, Patrick Dung wrote:
> Hi,
>
> I would like to know why quota is not enabled in the stock kernel..
>
> I remembered that it is not enabled since freebsd 3.5 or freebsd 4 generation.
> Now in freebsd 9.0, it still neeed a kernel rebuild.
>
> I have heard i
On 25 December 2012 10:07, Konstantin Belousov wrote:
> Enabling quota by default would cause small overhead, like one mutex acquire,
> for each inode and block alloc/dealloc, even for mount without quotas enabled.
Why is this, and can it be avoided (for mounts without quotas)?
> Might be, it is
On Tue, Dec 25, 2012 at 10:23:26AM -0500, Eitan Adler wrote:
> On 25 December 2012 10:07, Konstantin Belousov wrote:
> > Enabling quota by default would cause small overhead, like one mutex
> > acquire,
> > for each inode and block alloc/dealloc, even for mount without quotas
> > enabled.
>
> W
On Mon, Dec 24, 2012 at 12:00:01PM +, freebsd-hackers-requ...@freebsd.org
wrote:
> Date: Sun, 23 Dec 2012 00:32:20 -0800
> From: John-Mark Gurney
> To: hack...@freebsd.org
> Subject: looking for someone to fix humanize_number (test cases
> included)
> Message-ID: <20121223083220.gl1...@
On Tue, Dec 25, 2012 at 07:20:37AM -1000, Clifton Royston wrote:
> On Mon, Dec 24, 2012 at 12:00:01PM +, freebsd-hackers-requ...@freebsd.org
> wrote:
> > From: John-Mark Gurney
> > To: hack...@freebsd.org
> > Subject: looking for someone to fix humanize_number (test cases
> > included)
>
On Tue, Dec 25, 2012 at 08:23:55AM -1000, Clifton Royston wrote:
> On Tue, Dec 25, 2012 at 07:20:37AM -1000, Clifton Royston wrote:
> > On Mon, Dec 24, 2012 at 12:00:01PM +,
> > freebsd-hackers-requ...@freebsd.org wrote:
> > > From: John-Mark Gurney
> > > To: hack...@freebsd.org
> > > Subject
On 25 December 2012 14:46, Clifton Royston wrote:
>> I correct myself: the function works fine, and there are no bugs I
> could find, though it's clear the man page could emphasize the correct
> usage a bit more.
Can you submit a diff to the man page as well? I figure if you got
confused at lea
> Which device drivers? We can't fix problems we don't know about.
ata(4) completely hung the system for 19 minutes (at which point
I manually intervened, see the PR), probably an infinite loop.
http://www.freebsd.org/cgi/query-pr.cgi?pr=170675
Siis(4) and ahci(4) have also caused data loss, pr
Hi,
If the driver is doing something daft like DELAY(x) in a fast
interrupt handler which would lead to that behaviour, it should be
fixed.
If it's doing a DELAY(x) in a critical section, it shuld be fixed.
Otherwise, a DELAY(x) in a driver only chews CPU; the scheduler can
preempt that. I don't
I am curious if other operating systems have this performance impact.
Could we have some workaround or need some code improvement?
For example:
Do the checking/accounting only if the specific mount point has enabled quota.
etc..
Regards,
Patrick
--- On Tue, 12/25/12, Konstantin Belousov wrote:
11 matches
Mail list logo