Displaying 13 results from an estimated 13 matches for "cache_hits".
Did you mean:
cache_hit
2006 Jul 03
1
Capistrano - disable_web and enable_web with lighty?
I was using lighty+fastcgi before, and it was working pretty well, but
I decided to move to Apache+mongrel because I really really like
Mongrel. Well now I found out about lighty+pound+mongrel [1] and I
think I''m going to give that a shot. I definitely prefer lighty to
Apache - it''s pretty ridiculous how much fewer resources it uses.
Anyway the only thing I''m going to
2014 Feb 06
0
Array Confusion
I have the following instruction that returns an array that I'm quite confused about. I can't even read it. Can someone shed some light as to how to reach into this array of hashes (that's what I can see) to get the location lat and lon?
res = Geocoder.search(addy1)
This is the res:
[#<Geocoder::Result::Google:0x007fb46c345e18
2017 Jun 21
2
Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
...efine dq_btime dq_dqb.dqb_btime
#define dq_itime dq_dqb.dqb_itime
#define dqoff(UID) ((loff_t)((UID) * sizeof (struct dqblk)))
#if _LINUX_QUOTA_VERSION < 2
struct dqstats
{
u_int32_t lookups;
u_int32_t drops;
u_int32_t reads;
u_int32_t writes;
u_int32_t cache_hits;
u_int32_t pages_allocated;
u_int32_t allocated_dquots;
u_int32_t free_dquots;
u_int32_t syncs;
};
#else
/* Flags that indicate which fields in dqinfo structure are valid. */
# define IIF_BGRACE 1
# define IIF_IGRACE 2
# define IIF_FLAGS 4
# define IIF_ALL (I...
2002 May 07
0
Re: SAMBA compile errors at XFS kernel.. (fwd)
...ffset of tree in file in blocks */
#define DQTREEDEPTH 4 /* Depth of quota tree */
#define DQSTRINBLK ((DQBLKSIZE - sizeof(struct disk_dqdbheader)) / sizeof(struct disk_dqblk)) /* Number of entries in one blocks */
struct dqstats {
__u32 lookups;
__u32 drops;
__u32 reads;
__u32 writes;
__u32 cache_hits;
__u32 allocated_dquots;
__u32 free_dquots;
__u32 syncs;
__u32 version;
};
#ifdef __KERNEL__
extern int nr_dquots, nr_free_dquots;
#define NR_DQHASH 43 /* Just an arbitrary number */
#define DQ_LOCKED 0x01 /* dquot under IO */
#define DQ_MOD 0x02 /* dquot modified sinc...
2017 Oct 17
0
Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
...me??????? dq_dqb.dqb_itime
>
> #define dqoff(UID)????? ((loff_t)((UID) * sizeof (struct dqblk)))
>
> #if _LINUX_QUOTA_VERSION < 2
> struct dqstats
> ? {
> ??? u_int32_t lookups;
> ??? u_int32_t drops;
> ??? u_int32_t reads;
> ??? u_int32_t writes;
> ??? u_int32_t cache_hits;
> ??? u_int32_t pages_allocated;
> ??? u_int32_t allocated_dquots;
> ??? u_int32_t free_dquots;
> ??? u_int32_t syncs;
> ? };
> #else
>
> /* Flags that indicate which fields in dqinfo structure are valid.? */
> # define IIF_BGRACE???? 1
> # define IIF_IGRACE???? 2
>...
2017 Jun 20
2
Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
Hi,
I have problem with quota storage information in dovecot-2.2.29 (and
newer versions, too - 2.2.30.2).
I use FS quota backend.
............................
# 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf
# OS: Linux 4.4.68-1 x86_64
mail_plugins = quota
plugin {
quota = fs:User quota:mount=/poczta:user
quota2 = fs:Group quota:mount=/poczta:group
}
protocol imap {
2020 Jun 16
0
[PATCH v5 2/2] mm, treewide: Rename kzfree() to kfree_sensitive()
As said by Linus:
A symmetric naming is only helpful if it implies symmetries in use.
Otherwise it's actively misleading.
In "kzalloc()", the z is meaningful and an important part of what the
caller wants.
In "kzfree()", the z is actively detrimental, because maybe in the
future we really _might_ want to use that "memfill(0xdeadbeef)" or
2020 Apr 13
0
[PATCH 1/2] mm, treewide: Rename kzfree() to kfree_sensitive()
As said by Linus:
A symmetric naming is only helpful if it implies symmetries in use.
Otherwise it's actively misleading.
In "kzalloc()", the z is meaningful and an important part of what the
caller wants.
In "kzfree()", the z is actively detrimental, because maybe in the
future we really _might_ want to use that "memfill(0xdeadbeef)" or
2020 Jun 16
0
[PATCH v4 2/3] mm, treewide: Rename kzfree() to kfree_sensitive()
As said by Linus:
A symmetric naming is only helpful if it implies symmetries in use.
Otherwise it's actively misleading.
In "kzalloc()", the z is meaningful and an important part of what the
caller wants.
In "kzfree()", the z is actively detrimental, because maybe in the
future we really _might_ want to use that "memfill(0xdeadbeef)" or
2020 Jun 16
3
[PATCH v5 0/2] mm, treewide: Rename kzfree() to kfree_sensitive()
v5:
- Break the btrfs patch out as a separate patch to be processed
independently.
- Update the commit log of patch 1 to make it less scary.
- Add a kzfree backward compatibility macro in patch 2.
v4:
- Break out the memzero_explicit() change as suggested by Dan Carpenter
so that it can be backported to stable.
- Drop the "crypto: Remove unnecessary
2020 Jun 16
14
[PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive()
v4:
- Break out the memzero_explicit() change as suggested by Dan Carpenter
so that it can be backported to stable.
- Drop the "crypto: Remove unnecessary memzero_explicit()" patch for
now as there can be a bit more discussion on what is best. It will be
introduced as a separate patch later on after this one is merged.
This patchset makes a global rename of the kzfree()
2020 Jun 16
14
[PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive()
v4:
- Break out the memzero_explicit() change as suggested by Dan Carpenter
so that it can be backported to stable.
- Drop the "crypto: Remove unnecessary memzero_explicit()" patch for
now as there can be a bit more discussion on what is best. It will be
introduced as a separate patch later on after this one is merged.
This patchset makes a global rename of the kzfree()
2020 Apr 13
10
[PATCH 0/2] mm, treewide: Rename kzfree() to kfree_sensitive()
This patchset makes a global rename of the kzfree() to kfree_sensitive()
to highlight the fact buffer clearing is only needed if the data objects
contain sensitive information like encrpytion key. The fact that kzfree()
uses memset() to do the clearing isn't totally safe either as compiler
may compile out the clearing in their optimizer. Instead, the new
kfree_sensitive() uses