qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH -V3 1/8] hw/9pfs: Add V9fsfidmap in preparation for adding fd reclaim
Date: Sun, 13 Mar 2011 20:53:41 +0000	[thread overview]
Message-ID: <AANLkTinAj3qr560QP7Hth4BRxCBUGqy13RN9T-aCvPCO@mail.gmail.com> (raw)
In-Reply-To: <87vczmq1qm.fsf@linux.vnet.ibm.com>

On Sun, Mar 13, 2011 at 7:06 PM, Aneesh Kumar K. V
<aneesh.kumar@linux.vnet.ibm.com> wrote:
> On Sun, 13 Mar 2011 15:46:29 +0000, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Sat, Mar 5, 2011 at 5:52 PM, Aneesh Kumar K.V
>> <aneesh.kumar@linux.vnet.ibm.com> wrote:
>> > @@ -185,17 +188,22 @@ typedef struct V9fsXattr
>> >     int flags;
>> >  } V9fsXattr;
>> >
>> > +typedef struct V9fsfidmap {
>>
>> V9fsFidMap (naming convention)
>>
>> > +    union {
>> > +        int fd;
>> > +        DIR *dir;
>> > +        V9fsXattr xattr;
>> > +    } fs;
>>
>> The name "fs" is not meaningful.
>>
>> > +    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;
>>
>> This name is confusing.  A "map" is usually a container that stores
>> key/value pairs.  V9fsFidMapEntry would be clearer.  But then I
>> thought that is what V9fsFidState is?
>
> I am bad at naming. I wanted to indicate something that can be shared
> across multiple fids and also indicate the local file system
> "mapping"/data. I will take any suggestion.

Where does sharing happen, I didn't notice any code that shares fds
between fids?

Stefan

  reply	other threads:[~2011-03-13 20:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 17:52 [Qemu-devel] [PATCH -V3 1/8] hw/9pfs: Add V9fsfidmap in preparation for adding fd reclaim Aneesh Kumar K.V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 2/8] hw/9pfs: Add file descriptor reclaim support Aneesh Kumar K.V
2011-03-13 16:08   ` Stefan Hajnoczi
2011-03-13 18:57     ` Aneesh Kumar K. V
2011-03-14 10:13       ` Stefan Hajnoczi
2011-03-15  8:35         ` Aneesh Kumar K. V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 3/8] hw/9pfs: Use v9fs_do_close instead of close Aneesh Kumar K.V
2011-03-13 16:10   ` Stefan Hajnoczi
2011-03-13 18:58     ` Aneesh Kumar K. V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 4/8] hw/9pfs: Implement syncfs Aneesh Kumar K.V
2011-03-13 16:24   ` Stefan Hajnoczi
2011-03-13 18:59     ` Aneesh Kumar K. V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 5/8] hw/9pfs: Add open flag to fid Aneesh Kumar K.V
2011-03-13 16:38   ` Stefan Hajnoczi
2011-03-13 19:01     ` Aneesh Kumar K. V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 6/8] hw/9pfs: Add directory reclaim support Aneesh Kumar K.V
2011-03-13 16:42   ` Stefan Hajnoczi
2011-03-13 19:02     ` Aneesh Kumar K. V
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 7/8] hw/9pfs: Add new virtfs option cache=none to skip host page cache Aneesh Kumar K.V
2011-03-13 17:23   ` Stefan Hajnoczi
2011-03-13 19:04     ` Aneesh Kumar K. V
2011-03-13 20:57       ` Stefan Hajnoczi
2011-03-15  8:36         ` Aneesh Kumar K. V
2011-03-14 10:20       ` Stefan Hajnoczi
2011-03-15  9:19         ` Aneesh Kumar K. V
2011-03-15 11:11           ` Stefan Hajnoczi
2011-03-15 12:30             ` Aneesh Kumar K. V
2011-03-16  8:59               ` Stefan Hajnoczi
2011-03-05 17:52 ` [Qemu-devel] [PATCH -V3 8/8] hw/9pfs: Skip file system sync if we have specified cache=none option Aneesh Kumar K.V
2011-03-13 15:46 ` [Qemu-devel] [PATCH -V3 1/8] hw/9pfs: Add V9fsfidmap in preparation for adding fd reclaim Stefan Hajnoczi
2011-03-13 19:06   ` Aneesh Kumar K. V
2011-03-13 20:53     ` Stefan Hajnoczi [this message]
2011-03-14 10:23       ` Stefan Hajnoczi
2011-03-15  9:20       ` Aneesh Kumar K. V
2011-03-15 10:38         ` Stefan Hajnoczi
2011-03-15 12:27           ` Aneesh Kumar K. V

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=AANLkTinAj3qr560QP7Hth4BRxCBUGqy13RN9T-aCvPCO@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.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).