From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: [Qemu-devel] Re: [PATCH -V2 1/6] hw/9pfs: Add V9fsfidmap in preparation for adding fd reclaim
Date: Tue, 01 Mar 2011 14:58:59 +0530 [thread overview]
Message-ID: <87ipw3gpes.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1298961534-8099-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Tue, 1 Mar 2011 12:08:49 +0530, "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
> diff --git a/hw/9pfs/virtio-9p.h b/hw/9pfs/virtio-9p.h
> index 2ae4ce7..2f49641 100644
> --- a/hw/9pfs/virtio-9p.h
> +++ b/hw/9pfs/virtio-9p.h
> @@ -101,7 +101,10 @@ enum p9_proto_version {
> #define P9_NOTAG (u16)(~0)
> #define P9_NOFID (u32)(~0)
> #define P9_MAXWELEM 16
> +#define P9_FD_RECLAIM_THRES 100
before merge we should change that to 1000. I have updated my local
tree. I kept it at 100 to make sure code path get tested when running
most of the test case.
>
> +#define FID_REFERENCED 0x1
> +#define FID_NON_RECLAIMABLE 0x2
> /*
> * ample room for Twrite/Rread header
> * size[4] Tread/Twrite tag[2] fid[4] offset[8] count[4]
> @@ -185,17 +188,22 @@ typedef struct V9fsXattr
> int flags;
> } V9fsXattr;
>
> +typedef struct V9fsfidmap {
> + union {
> + int fd;
> + DIR *dir;
> + V9fsXattr xattr;
> + } fs;
> + int fid_type;
> + V9fsString path;
> + int flags;
> +} V9fsFidMap;
> +
> struct V9fsFidState
> {
> - int fid_type;
> int32_t fid;
> - V9fsString path;
> - union {
> - int fd;
> - DIR *dir;
> - V9fsXattr xattr;
> - } fs;
> uid_t uid;
> + V9fsFidMap fsmap;
> V9fsFidState *next;
> };
>
-aneesh
prev parent reply other threads:[~2011-03-01 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 6:38 [Qemu-devel] [PATCH -V2 1/6] hw/9pfs: Add V9fsfidmap in preparation for adding fd reclaim Aneesh Kumar K.V
2011-03-01 6:38 ` [Qemu-devel] [PATCH -V2 2/6] hw/9pfs: Add file descriptor reclaim support Aneesh Kumar K.V
2011-03-01 6:38 ` [Qemu-devel] [PATCH -V2 3/6] hw/9pfs: Use v9fs_do_close instead of close Aneesh Kumar K.V
2011-03-01 6:38 ` [Qemu-devel] [PATCH -V2 4/6] hw/9pfs: Implement syncfs Aneesh Kumar K.V
2011-03-01 10:22 ` Stefan Hajnoczi
2011-03-01 15:02 ` Aneesh Kumar K. V
2011-03-01 15:59 ` Stefan Hajnoczi
2011-03-01 18:02 ` Aneesh Kumar K. V
2011-03-01 20:27 ` Stefan Hajnoczi
2011-03-02 5:05 ` Aneesh Kumar K. V
2011-03-02 10:20 ` Stefan Hajnoczi
2011-03-02 11:28 ` Aneesh Kumar K. V
2011-03-01 6:38 ` [Qemu-devel] [PATCH -V2 5/6] hw/9pfs: Add open flag to fid Aneesh Kumar K.V
2011-03-01 6:38 ` [Qemu-devel] [PATCH -V2 6/6] hw/9pfs: Add directory reclaim support Aneesh Kumar K.V
2011-03-01 9:28 ` Aneesh Kumar K. V [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipw3gpes.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).