All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: Andrew Warfield <andrew.warfield@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Turn blktap tapfds into a link list
Date: Fri, 29 Sep 2006 14:32:29 -0400	[thread overview]
Message-ID: <451D66BD.3040205@redhat.com> (raw)
In-Reply-To: <eacc82a40609291013x72ed2cf0x77e3e6b977146005@mail.gmail.com>

Andrew Warfield wrote:
> Hi Steven,
> 
>   thanks for getting to this so quickly!  The patch generally looks good 

Thanks, it was some what fresh in my head, so I decided to dump it out.

> -- a
> couple of quick thoughts:
> 
>  - Linear searches of the tapfds list are a little grim where they 
> appear in
>    the data path (blktap_ioctl, blktap_kick_user, fast_flush_area,

I didn't like this either.  Perhaps I could switch it back to an array 
of pointers.  And I could even have the array be able to resize, with 
the use of rcu locks.

>    do_block_io_op, dispatch_rw_block_io).  If we are happy with a limit of
>    254 concurrent devices for the immediate term, I wonder if a lookup 
> array
>    indexed by minor and allocated on use might be better?

Yeah, I think I do agree with you on this.  I really don't like that 
linear search.  Maybe I did it because I was tired and it seemed cool. ;)

> 
>  - I enjoyed seeing the domid_translate array go away, I think we can kill
>    this translation all together though by moving the domid/busid lookup
>    out of blktapctrl and into xenbus, and filling it in directly when a
>    new vbd is connected.

This is a separate issue, and would need to be looked at later. (I'm not 
to sure on the interworkings of that code).

> 
>  - With dynamic allocation, MAX_TAP_DEV seems a little unnecessary.  
> Shouldn't
>    we just allocate until we run out of minors now?

Sure! I just was keeping it in sync with what was there.  The old code 
didn't allocate more than MAX_TAP_DEV so I wasn't about to change it.

> 
> This is a great improvement.  I know of at least one person that is 
> regularly
> running blktap with 60-80 vbds -- I'd like to get them to try out the 
> patch as
> an additional check.  Also, because of the changes in allocation and 
> locking
> I'm inclined to wait until immediately after the 3.0.3 barrier with this 
> one.
> Sound okay?

Sounds fine with me.  Thanks,

-- Steve

  reply	other threads:[~2006-09-29 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  4:00 [PATCH] Turn blktap tapfds into a link list Steven Rostedt
2006-09-29 17:13 ` Andrew Warfield
2006-09-29 18:32   ` Steven Rostedt [this message]
2006-09-29 18:41     ` Andrew Warfield

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=451D66BD.3040205@redhat.com \
    --to=srostedt@redhat.com \
    --cc=andrew.warfield@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.